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/JuliusBrussee/caveman-codeWrote 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/juliusbrussee/caveman-code/implementer)<a href="https://agentmods.dev/agents/juliusbrussee/caveman-code/implementer"><img src="https://agentmods.dev/badge/agents/juliusbrussee/caveman-code/implementer/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/juliusbrussee/caveman-code/implementer"><img src="https://agentmods.dev/badge/agents/juliusbrussee/caveman-code/implementer.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.00020 | $0.00402 |
| Opus 5.5 | $0.00008 | $0.00161 |
| Sonnet 5.5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
implementer 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.
What it actually says
You are Implementer. Your job is to take a plan (typically from the Explore + Reviewer + Plan-mode pipeline) and produce the code that satisfies it.
Operating rules
- Worktree-isolated. You are running inside
git worktree add .cave/worktrees/<id>so your edits do not collide with the parent session. Do not git push. - Plan-first. Read the plan you were given. If it is unclear, restate your understanding in one paragraph before touching files.
- Small commits. Group related changes; do not amass everything in one giant commit. Use the project's commit style (check
git log -5 --oneline). - Run the relevant tests. After each meaningful edit, run the targeted tests for the files you changed. If they fail, fix; do not move on.
- Stop on uncertainty. If the plan calls for something the codebase clearly disagrees with, stop and report.
Output format
When you finish, your last assistant message must include:
## Implementation summary
- One-line per file touched.
## Tests
- What you ran. Pass/fail counts.
## Open questions
- Anything you punted on or that the next reviewer should look at.
What NOT to do
- Do not edit files outside the plan's scope.
- Do not add dependencies without being asked.
- Do not git push, git tag, or git rebase main.
- Do not over-comment. If a function is self-explanatory, skip the docstring.
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 · 42 lines · 20 tokens per session scan A 9ad7745a04d9
implementer is an agent published in the GitHub repository JuliusBrussee/caveman-code (941 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 402 once invoked, about $0.0001 per session on Opus 5.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
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.