jans23
jans23'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 @jans23 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 odoo-modules corpus
Nitrokey/odoo-modules: Custom modules for Odoo
- Reuse a worked example: the commit “website_mass_mailing_double_opt_in_nitrokey: add tests, remove dead o…” (5 files · Python).
- Answer from odoo-modules's real Python source instead of memory (API design and specification).
- What does website_mass_mailing_double_opt_in_nitrokey do in odoo-modules?
Search the GitHub repository Nitrokey/odoo-modules with XERJ (https://hub.xerj.org/corpus/nitrokey--odoo-modules). 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/Nitrokey/odoo-modules odoo-modules && git -C odoo-modules checkout 164fdad740a76fe05a7c5b0e6bffa1229067acbb 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./odoo-modules --url http://127.0.0.1:9200 --prefix odoo-modules --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: AGPL-3.0. Read it for the approach only, do not copy code.
corpus nitrokey--odoo-modules · API design and specification
Related corpora: swift-book, box-openapi, postman-collection, api-blueprint
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
Nitrokey/odoo-modules
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/jans23)
Included with the author's permission (email, 2026-10-22), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.