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/explain-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.00009 | $0.00182 |
| Opus 5 | $0.00005 | $0.00091 |
| Sonnet 5 | $0.00002 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
explain-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:
- explain — 91% identical, 4 lines differ
What it actually says
Input
Arguments: $ARGUMENTS
Task
Search the knowledge base to find relevant content, then provide a clear explanation.
-
Call
mcp__plugin_quarry-dev_quarry__findwith a query derived from the arguments. If the arguments look like a document name (has a file extension like.pdf,.md,.py), also setdocument_filterto the document name. -
Using the search results, provide a clear, concise explanation of the document or topic. If results span multiple documents, synthesize across them. Cite specific documents and page numbers in your explanation.
-
If no results are found, say so and suggest the user ingest the relevant content first with
/ingest-dev.
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 · 20 lines · 9 tokens per session scan A a3829634adfe
explain-dev is a command published in the GitHub repository punt-labs/quarry (3 stars, last pushed 2d ago), licensed MIT. It adds 9 tokens to every session and 182 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.