Mike Levin http://MikeLev.in
Mike Levin http://MikeLev.in'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 @miklevin 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 pipulate corpus
pipulate/pipulate: Local First AI SEO Software on Nix, FastHTML & HTMX
- Look up how pipulate implements ai, fasthtml, htmx, with answers cited to file and line.
- Reuse a worked example: the commit “implement honeybot live messages and voice over” (5 files · Python, Nix).
- Answer from pipulate's real Python source instead of memory (AI, prompts and agents).
- Where does pipulate handle “implement honeybot live messages and voice over”?
- How does pipulate implement ai?
- What does remotes do in pipulate?
Search the GitHub repository pipulate/pipulate with XERJ (https://hub.xerj.org/corpus/pipulate--pipulate). 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/pipulate/pipulate pipulate && git -C pipulate checkout fe879c5ba784fdd282bc40d80067cad994451ebf 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./pipulate --url http://127.0.0.1:9200 --prefix pipulate --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 pipulate--pipulate · AI, prompts and agents
Related corpora: adalflow, cognita, pipeshub-ai/pipeshub-ai, aceFelix/jarvis
AI search and retrieval with XERJ · Case study: reference coding for agents
Selected work
pipulate/pipulate
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/miklevin)
Included with the author's permission (email, 2026-10-19), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.