endorses
endorses'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 @endorses 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 lippycat corpus
endorses/lippycat: Network traffic capture and protocol analysis in Go. CLI and TUI for local or distributed monitoring of VoIP, DNS, HTTP, TLS, email, and…
- Reuse a worked example: the commit “support central task selection and capture-source export” (77 files · Go, protobuf).
- Answer from lippycat's real Go source instead of memory (Networking, protocols and serialisation).
- Where does lippycat handle “support central task selection and capture-source export”?
- What does internal/pkg do in lippycat?
Search the GitHub repository endorses/lippycat with XERJ (https://hub.xerj.org/corpus/endorses--lippycat). 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/endorses/lippycat lippycat && git -C lippycat checkout 8fd1b34508107751f36ee79201c8aafce0bf8f1f 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./lippycat --url http://127.0.0.1:9200 --prefix lippycat --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 endorses--lippycat · Networking, protocols and serialisation
Related corpora: caddy, curl-src, connect-go, hivemq-mqtt-client
Case study: reference coding for agents
Selected work
endorses/lippycat
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/endorses)
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.