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/capitalone/context-specs/querygit clone --depth 1 https://github.com/capitalone/context-specsWhat 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.00059 | $0.01520 |
| Opus 5 | $0.00030 | $0.00760 |
| Sonnet 5 | $0.00012 | $0.00304 |
| Haiku 4.5 | $0.00006 | $0.00152 |
Grade A, and why
query 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/query
Read CLAUDE.md first for the layered structure and hard rules. Critical rule for this command: search wiki/ only — never read from raw/. Synthesis-at-ingest is the whole point of the wiki; if a question can't be answered from wiki/, the right answer is "ingest more sources," not "let me go read the raw docs."
Arguments: $ARGUMENTS
The argument is the natural-language question. If $ARGUMENTS is empty, ask the user for their question and stop.
Step 1 — Topology pass (read MOC first)
Before grepping, read wiki/MOC.md end-to-end. MOC is the curated map of the vault — it tells you which clusters/sections exist and which pages are considered canonical entry points for each area. Note which sections are most relevant to the question; you'll use them to weight grep results in step 2 and to notice gaps (e.g. "MOC has no section that covers this question — that itself is a finding").
If MOC obviously hasn't been updated for pages you encounter later (e.g. step 2 surfaces a clearly-relevant page that MOC doesn't link), flag this in your final answer as a lint-worthy finding so the user knows MOC is drifting.
Step 2 — Find the seed pages
Identify keywords/concepts in the question. Use Grep over wiki/ (NOT raw/) to find candidate pages. Match against:
- Filenames (slugs).
- H1 titles.
aliases:frontmatter values.- First paragraph / Definition section text.
Score candidates by:
- How directly the page addresses the question (keyword density, definition match).
- Whether MOC lists it under a section the question maps to (boost).
Take the top ~5 as seed pages.
Step 3 — Walk the link graph (2 hops)
For each seed page, read it. Follow outgoing [[wikilinks]] to add neighbors to the working set. Then follow links one more hop. Cap the working set at ~15 pages — beyond that, the question is too broad, narrow it.
While reading, note:
- Which pages contain claims relevant to the question.
- Which sources (
[[<source-slug>]]) those claims cite. - Any contradictions or open questions surfaced by the pages.
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 · 113 lines · 59 tokens per session scan A 42737b15801f
query is a command published in the GitHub repository capitalone/context-specs (41 stars, last pushed 8d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,520 once invoked, about $0.0003 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-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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.