Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Hurricane0698/zotWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/hurricane0698/zot/vault-ingest)<a href="https://agentmods.dev/commands/hurricane0698/zot/vault-ingest"><img src="https://agentmods.dev/badge/commands/hurricane0698/zot/vault-ingest.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00229 |
| Opus 5 | $0.00000 | $0.00114 |
| Sonnet 5 | $0.00000 | $0.00046 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade B, and why
vault-ingest scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
7. Leave an active-output prompt under `kb/human/active-output/**` unless the user explicitly declines. What it actually says
Ingest new material into the current zot vault.
Arguments: $ARGUMENTS
Workflow:
- Resolve the vault path from
ZOT_VAULT, then legacyOMEGA_VAULT. - Read the vault's
AGENTS.mdfirst when it exists. - Keep raw captures under
kb/raw/**; do not overwrite them. - Write durable synthesis under
kb/wiki/**. - Update
kb/meta/index.mdwhen a new durable page is created. - Append a log entry to
kb/meta/log.md. - Leave an active-output prompt under
kb/human/active-output/**unless the user explicitly declines. - Run
"$ZOT_VAULT/scripts/kb-lint"after the changes.
If $ARGUMENTS names a source, use it as the title or ingest target. If it is empty, ask the user what should be captured.
Guardrail:
- Keep this command focused on one source or one small coherent batch. If the task expands into restructure, query promotion, or feedback triage, switch to
vault-wiki.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 19 lines · 0 tokens per session scan B 89bad86f3ee9
vault-ingest is a command published in the GitHub repository Hurricane0698/zot (99 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 229 tokens. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.