silverhand
silverhand'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 @lunalully 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 lunatic corpus
lunalully/lunatic: Reconhecimento passivo de subdominios em Go: consulta apenas fontes OSINT de terceiros, nunca toca no alvo
- Look up how lunatic implements bug-bounty, bugbounty, cybersecurity, with answers cited to file and line.
- Reuse a worked example: the commit “Novo banner e saída limpa sem nomes de fontes” (6 files · Go).
- Answer from lunatic's real Go source instead of memory (Security and vulnerabilities).
- Where does lunatic handle “Novo banner e saída limpa sem nomes de fontes”?
- How does lunatic implement bug-bounty?
- What does internal/banner do in lunatic?
Search the GitHub repository lunalully/lunatic with XERJ (https://hub.xerj.org/corpus/lunalully--lunatic). 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/lunalully/lunatic lunatic && git -C lunatic checkout 7fd51a4cdee18128bdcff5bc4b09b031df89a86f 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./lunatic --url http://127.0.0.1:9200 --prefix lunatic --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 lunalully--lunatic · Security and vulnerabilities
Related corpora: grpc-go, certstrap, potato-security/PotatoTool, gigioneggiando/argo
Code security audit with XERJ · Case study: reference coding for agents
Selected work
lunalully/lunatic
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/lunalully)
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.