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/quarry-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.00005 | $0.00475 |
| Opus 5 | $0.00003 | $0.00237 |
| Sonnet 5 | $0.00001 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
quarry-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 3d 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.
What it actually says
Input
Arguments: $ARGUMENTS
Parse the first token as a subcommand. Default to status if empty.
Subcommands
- status (default): Call
mcp__plugin_quarry-dev_quarry__status - sync: Run
quarry syncvia the Bash tool withrun_in_background: true. This avoids blocking the conversation during long syncs. You will be notified when it completes. If a non-default database was selected viause, pass--db <name>to the CLI command. - collections: Call
mcp__plugin_quarry-dev_quarry__listwithkindset to"collections" - databases: Call
mcp__plugin_quarry-dev_quarry__listwithkindset to"databases" - registrations: Call
mcp__plugin_quarry-dev_quarry__listwithkindset to"registrations" - use
<name>: Callmcp__plugin_quarry-dev_quarry__usewithnameset to the second token. If no name is given afteruse, reply with brief usage:/quarry use <database-name> - enable: Run
quarry enablevia the Bash tool. If a directory argument follows, pass it as a positional argument. Supports--collection <name>to override the collection name. - disable: Run
quarry disablevia the Bash tool. If a directory argument follows, pass it as a positional argument. Supports--keep-datato preserve indexed data in LanceDB.
Output
For sync: after launching the background command, briefly confirm it's running (e.g., "Syncing in background — you'll be notified when done."). Do not block or poll.
For all other subcommands: 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.
- 3d ago First seen · 29 lines · 5 tokens per session scan A 65605df05416
quarry-dev is a command published in the GitHub repository punt-labs/quarry (3 stars, last pushed 3d ago), licensed MIT. It adds 5 tokens to every session and 475 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
implement
yes, thank you! please proceed with implementation.
create-forwarding-rule
Create a ZPA client forwarding policy rule to bypass or intercept traffic.
check-dev
Type-check a Z specification with fuzz.
test-dev
Validate and animate a Z specification with probcli.
search
Full-text search the carrel desk index (FTS5, bm25-ranked) for local files matching a query.
spec-plan
Run a resumable spec interview to produce spec.json/spec.md (planning-time), then optionally compile to prd.json. Usage: /plan-cascade:spec-plan " " [--output-dir ] [--flow ] [--first-principles] [--max-questions N] [--feature-slug ] [--compile] [--tdd ] [--confirm] [--no-confirm].