Mridul
Mridul'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 @DevForge255 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 lumen corpus
holoviz/lumen: Illuminate your data. Agent framework turning natural language into SQL, charts, dashboards and reports
- Look up how lumen implements ai-agents, conversational-ai, data-exploration, with answers cited to file and line.
- Reuse a worked example: the commit “add column-level lineage provenance to SQL result inspector…” (4 files · Python).
- Answer from lumen's real Python source instead of memory (AI, prompts and agents).
- How does lumen implement ai-agents?
- What does lumen do in lumen?
Search the GitHub repository holoviz/lumen with XERJ (https://hub.xerj.org/corpus/holoviz--lumen). 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/holoviz/lumen lumen && git -C lumen checkout 9d9de116c6308c27811152c10a429e0199af8ddc 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./lumen --url http://127.0.0.1:9200 --prefix lumen --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: BSD-3-Clause. Keep the copyright notice and credit the authors.
corpus holoviz--lumen · AI, prompts and agents
Related corpora: anything-llm, controlflow, GitTanish/Insight, mloda-ai/mloda
AI search and retrieval with XERJ · Case study: reference coding for agents
Selected work
holoviz/lumen
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/DevForge255)
Included with the author's permission (email, 2026-10-23), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.