ikagzy
ikagzy'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 @ikagzy 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 k-launcher corpus
ikagzy/k-launcher: open source for k-launcher
- Reuse a worked example: the commit “Add files via upload” (19 files · C#).
- Answer from k-launcher's real C# source instead of memory (API design and specification).
- Where does k-launcher handle “Add files via upload”?
- What does Kagzy-Launcher-Source do in k-launcher?
Search the GitHub repository ikagzy/k-launcher with XERJ (https://hub.xerj.org/corpus/ikagzy--k-launcher). 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/ikagzy/k-launcher k-launcher && git -C k-launcher checkout 08b946dfe5fd11e1e867266bf93291efa07f175c 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./k-launcher --url http://127.0.0.1:9200 --prefix k-launcher --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: GPL-3.0. Read it for the approach only, do not copy code.
corpus ikagzy--k-launcher · API design and specification
Related corpora: openapi-moonwalk, spectral, ibm-openapi-validator, msft-api-guidelines
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
ikagzy/k-launcher
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/ikagzy)
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.