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/juliusbrussee/cavekit/specgit clone --depth 1 https://github.com/JuliusBrussee/cavekitWhat 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.00018 | $0.00172 |
| Opus 5 | $0.00009 | $0.00086 |
| Sonnet 5 | $0.00004 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
spec 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.
What it actually says
Invoke the spec skill (skills/spec/SKILL.md). Treat $ARGUMENTS as the mode:
an idea → NEW, from-code → DISTILL, bug: <cause> → BACKPROP, amend <§X.n> →
targeted edit. spec is the sole mutator — it also writes the handoff blocks that
grill (§G/§C), research (§R), review (§V), and deepen (§I/§V/§T) produce. Caveman
encoding per FORMAT.md; sectioned ownership; show a diff, write on OK.
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 · 11 lines · 18 tokens per session scan A 484430ad3395
spec is a command published in the GitHub repository JuliusBrussee/cavekit (1,141 stars, last pushed 18d ago), licensed MIT. It adds 18 tokens to every session and 172 once invoked, about $0.0001 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
speckit.verify-tasks
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
archive
Archive merged feature specs into project memory with provenance, sweep discovery, and gated cleanup.
verify
Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.
retrospective
Perform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.
doctor
Validate project health: templates, agent config, Python runner/helpers, constitution, and feature artifacts.
validate
Verify spec-to-task traceability and check that completed tasks produced expected files.