shmuel biller
shmuel biller'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 @shmuelbiller1 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 TOKENFORGE corpus
shmuelbiller1/TOKENFORGE: shmuelbiller1/TOKENFORGE (JavaScript)
- Reuse a worked example: the commit “Add evidence-first offline R&D revision history” (4 files · Python).
- Answer from TOKENFORGE's real Python source instead of memory (API design and specification).
- Where does TOKENFORGE handle “Add evidence-first offline R&D revision history”?
- What does backend do in TOKENFORGE?
Search the GitHub repository shmuelbiller1/TOKENFORGE with XERJ (https://hub.xerj.org/corpus/shmuelbiller1--tokenforge). 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/shmuelbiller1/TOKENFORGE TOKENFORGE && git -C TOKENFORGE checkout 7f2049abcdb91026365e643c2a3e18d8bd3c9dc7 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./TOKENFORGE --url http://127.0.0.1:9200 --prefix tokenforge --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 shmuelbiller1--tokenforge · API design and specification
Related corpora: json-schema-test-suite, kubernetes-community, rust-api-guidelines, openapi-spec
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
shmuelbiller1/TOKENFORGE
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/shmuelbiller1)
Included with the author's permission (email, 2026-10-20), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.