Agrima
Agrima'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 @agcodes0315 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 Relaython corpus
agcodes0315/Relaython: Amazon Developer Hackathon
- Reuse a worked example: the commit “harden Relay Shield security boundaries” (3 files · Python).
- Answer from Relaython's real Python source instead of memory (API design and specification).
- Where does Relaython handle “harden Relay Shield security boundaries”?
- What does tests do in Relaython?
Search the GitHub repository agcodes0315/Relaython with XERJ (https://hub.xerj.org/corpus/agcodes0315--relaython). 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/agcodes0315/Relaython Relaython && git -C Relaython checkout 41316eb97b56d27ac4fc3d6e92df8cbd9ec2437b 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./Relaython --url http://127.0.0.1:9200 --prefix relaython --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 agcodes0315--relaython · API design and specification
Related corpora: rust-api-guidelines, graphql-over-http, redocly-cli, adyen-openapi
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
agcodes0315/Relaython
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/agcodes0315)
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.