Belky
Belky'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 @belky-me 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 vamp-k8s-audit corpus
Vampsecure-Labs/vamp-k8s-audit: Kubernetes security auditor: RBAC, pods, network, CIS Benchmark YAML engine (44+ checks), kube-bench wrapper, --delta diff scan
- Look up how vamp-k8s-audit implements cloud-security, container-security, devsecops, with answers cited to file and line.
- Reuse a worked example: the commit “motor YAML extensible v3.0.0: 26 checks CIS K8s + kube-bench w…” (5 files · Python).
- Answer from vamp-k8s-audit's real Python source instead of memory (Operations and SRE).
- How does vamp-k8s-audit implement cloud-security?
- What does vamp_k8s_audit do in vamp-k8s-audit?
Search the GitHub repository Vampsecure-Labs/vamp-k8s-audit with XERJ (https://hub.xerj.org/corpus/vampsecure-labs--vamp-k8s-audit). 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/Vampsecure-Labs/vamp-k8s-audit vamp-k8s-audit && git -C vamp-k8s-audit checkout c8c77671f6b7c5474a1488e3661777bfd3ea7d78 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./vamp-k8s-audit --url http://127.0.0.1:9200 --prefix vamp-k8s-audit --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 vampsecure-labs--vamp-k8s-audit · Operations and SRE
Related corpora: cloudnative-pg, kics, kaaval/kaaval, OWASP/wrongsecrets
Operational intelligence with XERJ · Case study: reference coding for agents
Selected work
Vampsecure-Labs/vamp-k8s-audit
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/belky-me)
Included with the author's permission (email, 2026-10-22), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.