linksinke
linksinke'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 @linksinke 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 toolbox corpus
linksinke/toolbox: 一个持续沉淀的日常工具箱,汇集脚本、配置模板、运维辅助工具和文件处理脚本,方便快速复用与维护。
- Reuse a worked example: the commit “新增mysql库表结构导出工具” (8 files · Python).
- Answer from toolbox's real Python source instead of memory (API design and specification).
- Where does toolbox handle “新增mysql库表结构导出工具”?
- What does dev工具集 do in toolbox?
Search the GitHub repository linksinke/toolbox with XERJ (https://hub.xerj.org/corpus/linksinke--toolbox). 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/linksinke/toolbox toolbox && git -C toolbox checkout 7cc5b6185221ab20d2af967eaa50348ec52411b2 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./toolbox --url http://127.0.0.1:9200 --prefix toolbox --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 linksinke--toolbox · API design and specification
Related corpora: graphql-composite-schemas-spec, redoc, postman-collection, googleapis
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
linksinke/toolbox
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/linksinke)
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.