X
X'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 @xscriptor 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 scripts corpus
xlnux/scripts: X Linux provisioning payload and CLI (x): phases, dotfiles, themes, migrations
- Look up how scripts implements archlinux, automation, bash, with answers cited to file and line.
- Reuse a worked example: the commit “add x agent install|status|remove for the Xscriptor AI b…” (6 files · shell).
- Answer from scripts's real shell source instead of memory (API design and specification).
- How does scripts implement archlinux?
- What does bin do in scripts?
Search the GitHub repository xlnux/scripts with XERJ (https://hub.xerj.org/corpus/equislinux--scripts). 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/xlnux/scripts scripts && git -C scripts checkout f5f446d28f31019d85ecbd361c4e84ae8f409ef2 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./scripts --url http://127.0.0.1:9200 --prefix scripts --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 equislinux--scripts · API design and specification
Related corpora: mkcert, caldera, BragatteMAS/os-postinstall-scripts, hakuimaku/hakuspace
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
xlnux/scripts
X Linux provisioning payload and CLI (x): phases, dotfiles, themes, migrations
The corpus is the whole repository at the pinned commit, not only the files of the selected commit.
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/xscriptor)
Included with the author's permission (email, 2026-10-08), under each repository's own licence, with attribution. Own more repositories? Sign in with GitHub and add them. Want something removed? Reply to the email, withdraw it on /add, or open an issue on xerj-org/xerj.