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.
npx agentmods add commands/punt-labs/quarry/help-devgit clone --depth 1 https://github.com/punt-labs/quarryWhat 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 | $0.00004 | $0.00163 |
| Opus 5 | $0.00002 | $0.00081 |
| Sonnet 5 | $0.00001 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
help-dev scanned grade A with 0 findings 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 2d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- help — 100% identical, 16 lines differ
What it actually says
Task
Print the table below verbatim. Do not run any tool.
Output
Command Description
─────────────────────────────────────────────────────────────
/quarry-dev:explain-dev Explain a document or topic from your knowledge base
/quarry-dev:find-dev Search your knowledge base
/quarry-dev:help-dev List quarry slash commands
/quarry-dev:ingest-dev Ingest a URL, directory, or file into your knowledge base
/quarry-dev:quarry-dev Manage your quarry knowledge base
/quarry-dev:remember-dev Remember inline text content in your knowledge base
/quarry-dev:source-dev Find the original document for a claim or topic
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.
- 2d ago First seen · 23 lines · 4 tokens per session scan A 0be727eee933
help-dev is a command published in the GitHub repository punt-labs/quarry (3 stars, last pushed 2d ago), licensed MIT. It adds 4 tokens to every session and 163 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
meeting-listen
Play back a completed meeting summary as a voiced debate between personas.
feedback
Incorporate feedback into PR/FAQ and redraft affected sections.
contracts-dev
Generate runtime contracts (preconditions, postconditions, invariants) from a Z specification.
review
Peer review a PR/FAQ document for quality and decision readiness.
streamline
Tighten a PR/FAQ by removing redundancy, weasel words, and bloat.
partition-dev
Derive test cases from Z specification using TTF testing tactics.