Shreyas
Shreyas'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 @kilqwe 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 hacktober-week-2 corpus
kilqwe/hacktober-week-2: Credit burn predictor for startups and solo devs: feed it your Terraform, get live-priced monthly costs, how many months your cloud credits
- Look up how hacktober-week-2 implements aws, cloud-cost, finops, with answers cited to file and line.
- Reuse a worked example: the commit “Added Bench tests and updated cred_pred to include ECS fargate” (3 files · Python).
- Answer from hacktober-week-2's real Python source instead of memory (Operations and SRE).
- Where does hacktober-week-2 handle “Added Bench tests and updated cred_pred to include ECS fargate”?
- How does hacktober-week-2 implement aws?
Search the GitHub repository kilqwe/hacktober-week-2 with XERJ (https://hub.xerj.org/corpus/kilqwe--hacktober-week-2). 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/kilqwe/hacktober-week-2 hacktober-week-2 && git -C hacktober-week-2 checkout dec5bbf529188605f7131546ddc19abc5c6a3bc5 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./hacktober-week-2 --url http://127.0.0.1:9200 --prefix hacktober-week-2 --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 kilqwe--hacktober-week-2 · Operations and SRE
Related corpora: infracost, cloud-custodian, moseleydev/swarm-kit, raphgm/cloudcost-cli
Operational intelligence with XERJ · Case study: reference coding for agents
Selected work
kilqwe/hacktober-week-2
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/kilqwe)
Included with the author's permission (email, 2026-10-21), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.