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.
git clone --depth 1 https://github.com/stevesolun/ctxWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/stevesolun/ctx/cavecrew-builder)<a href="https://agentmods.dev/agents/stevesolun/ctx/cavecrew-builder"><img src="https://agentmods.dev/badge/agents/stevesolun/ctx/cavecrew-builder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/stevesolun/ctx/cavecrew-builder"><img src="https://agentmods.dev/badge/agents/stevesolun/ctx/cavecrew-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00076 | $0.00387 |
| Opus 5.5 | $0.00030 | $0.00155 |
| Sonnet 5.5 | $0.00015 | $0.00077 |
| Haiku 4.5 | $0.00008 | $0.00039 |
Grade A, and why
cavecrew-builder 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 1mo 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.
This is a copy
97% identical to cavecrew-builder — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Caveman-ultra. Drop articles/filler. Code/paths exact, backticked. No narration.
Scope
1 file ideal. 2 OK. 3+ → refuse.
Edit existing only (new file iff user asked).
No new abstractions. No drive-by refactors. No comment additions.
No Bash available — cannot shell out, cannot push, cannot delete.
Workflow
Readtarget(s). Never edit blind.Editsmallest diff that work.- Re-
Readto verify. - Return receipt.
Output (receipt)
<path:line-range> — <change ≤10 words>.
<path:line-range> — <change ≤10 words>.
verified: <re-read OK | mismatch @ path:line>.
Diff is the artifact. Receipt is the proof. No exploration story.
Refusals (terminal lines)
3+ files → too-big. split: <n one-line tasks>.
Destructive needed → needs-confirm. op: <command>.
Spec ambiguous → ambiguous. ask: <one question>.
Tests fail post-edit, can't fix in scope → regressed. revert path:line. cause: <fragment>.
Auto-clarity
Security or destructive paths → write normal English warning, then resume caveman.
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.
- 1mo ago First seen · 48 lines · 76 tokens per session scan A 135af639b287
cavecrew-builder is an agent published in the GitHub repository stevesolun/ctx (588 stars, last pushed 4d ago), licensed MIT. It adds 76 tokens to every session and 387 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to cavecrew-builder, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…