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/find-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.00224 |
| Opus 5 | $0.00002 | $0.00112 |
| Sonnet 5 | $0.00001 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
find-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:
- find — 94% identical, 2 lines differ
What it actually says
Input
Arguments: $ARGUMENTS
Use the full arguments text as the search query.
Task
Call mcp__plugin_quarry-dev_quarry__find with query set to the arguments.
If the result says "No results", say so briefly.
Determine the query type:
-
Question — the query asks for an answer (starts with who/what/how/why/when/where, ends with
?, or contains phrases like "is the", "how to", "how do"): provide a concise direct answer based on the search results, citing the source document and page number for each claim. Do not dump the raw results. -
Keywords — the query is exploratory (keywords, phrases, topic names): emit the tool output exactly as returned — character for character, including the leading ▶ unicode character. Do not reformat, add commentary, wrap in code fences, convert to markdown tables, or add boxes around the output.
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 · 24 lines · 4 tokens per session scan A f506a5c446e0
find-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 224 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
feedback
Incorporate feedback into PR/FAQ and redraft affected sections.
feedback-to-us
Tell us how the prfaq plugin is working for you (anonymous 1-5 feedback).
meeting
Run a simulated PR/FAQ review meeting with agentic personas.
quality
Improve test coverage, fix tests, optimize performance, reduce bundle size.
release
Publish new version and monitor release process.
review
Peer review a PR/FAQ document for quality and decision readiness.