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/caveman-code/migrategit clone --depth 1 https://github.com/JuliusBrussee/caveman-codeWhat 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.00013 | $0.00307 |
| Opus 5 | $0.00006 | $0.00153 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
migrate 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
Execute a code migration named $1 (target: ${2:-latest}).
Generic migration playbook (apply iff the named migration matches one of these shapes; otherwise plan first):
- Snapshot. Confirm the working tree is clean — abort if not.
- Inventory. Search for every occurrence of the deprecated symbol / pattern. Report counts grouped by file. Pause for user approval.
- Plan. List the migration in 3–7 numbered steps. Each step must be:
- Reviewable in isolation.
- Independently testable (or explicitly marked "no test possible").
- Execute step-by-step. After each step:
- Run the affected tests.
- Run the type-checker.
- Stop on the first failure and ask the user before proceeding.
- Verify. Run the full test suite and any project-specific lints.
- Document. Append a CHANGELOG entry under
## Unreleased.
Hard rules:
- Never combine multiple steps into one commit.
- Never disable tests "temporarily" — fix or revert.
- Pin third-party version bumps to exact versions during migration; relax the pin in a follow-up PR.
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 · 36 lines · 13 tokens per session scan A e5082f7e560b
migrate is a command published in the GitHub repository JuliusBrussee/caveman-code (929 stars, last pushed 18d ago), licensed MIT. It adds 13 tokens to every session and 307 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.