Aditya Raj Kar
Aditya Raj Kar's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.
Totals across every corpus @TRITUSLegend appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.
What an agent can do with the OpinionMap corpus
TRITUSLegend/OpinionMap: An AI-powered, multi-agent market intelligence platform that autonomously scrapes, analyzes, and visualizes real-time sentiment and trends…
- Reuse a worked example: the commit “chat page with cited answers, entry points and landing …” (12 files · TypeScript).
- Answer from OpinionMap's real TypeScript source instead of memory (AI, prompts and agents).
- What does frontend do in OpinionMap?
Search the GitHub repository TRITUSLegend/OpinionMap with XERJ (https://hub.xerj.org/corpus/trituslegend--opinionmap). Run these in a shell, in order, and check each result before the next: 1. xerj --help (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh 2. git clone https://github.com/TRITUSLegend/OpinionMap OpinionMap && git -C OpinionMap checkout 5341a9579ad0e0c973cbc3f183b158d733926d61 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./OpinionMap --url http://127.0.0.1:9200 --prefix opinionmap --progress plain 5. xerj autoindex map --url http://127.0.0.1:9200 Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt Licence: MIT. Keep the copyright notice and credit the authors.
corpus trituslegend--opinionmap · AI, prompts and agents
Related corpora: distilabel, gpt-engineer, atomic-agents, flagembedding
AI search and retrieval with XERJ · Case study: reference coding for agents
Selected work
TRITUSLegend/OpinionMap
The corpus is the whole repository at the pinned commit, not only the files of the selected commit.
Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.
Sign in with GitHub or Hugging Face to see more: every selected commit in full (commit date, every folder, licence review state, pin) and the pack builds of each corpus.
[](https://hub.xerj.org/contributors/TRITUSLegend)
Included with the author's permission (email, 2026-10-19), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.