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 agents/stevesolun/ctx/cavecrew-buildergit clone --depth 1 https://github.com/stevesolun/ctxWhat 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.00076 | $0.00387 |
| Opus 5 | $0.00038 | $0.00193 |
| Sonnet 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 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- lean-crew-builder — 91% identical, 8 lines differ
- tldrcrew-builder — 89% identical, 8 lines differ
- graphcrew-builder — 88% identical, 22 lines differ
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.
- 2d ago First seen · 48 lines · 76 tokens per session scan A 135af639b287
cavecrew-builder is an agent published in the GitHub repository stevesolun/ctx (581 stars, last pushed 8d ago), licensed MIT. It adds 76 tokens to every session and 387 once invoked, about $0.0004 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 agents, from other repositories
AGENTS
The core Agents SDK, published to npm as agents. This is the most complex package in the monorepo.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
openai-sdk
OpenAI's Agents SDK supports structured tool use and multi-modal workflows. ContextForge can serve as a unified tool registry for OpenAI agents.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.