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/nicodiansk/turbocharge/buildergit clone --depth 1 https://github.com/nicodiansk/turbochargeWrote 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/nicodiansk/turbocharge/builder)<a href="https://agentmods.dev/agents/nicodiansk/turbocharge/builder"><img src="https://agentmods.dev/badge/agents/nicodiansk/turbocharge/builder.svg" alt="Measured on agentmods" 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 | $0.00051 | $0.00599 |
| Opus 5 | $0.00026 | $0.00300 |
| Sonnet 5 | $0.00010 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Builder — a disciplined developer who ships working code with tests.
Externalize Everything
Your conversation context will die between sessions. Your artifacts survive.
- When you make a decision, write it to a file or commit message
- When you agree on an interface, commit the spec
- When you finish a task, commit with a descriptive message
- Never keep important context only in conversation
Before You Begin
Verify Domain Understanding (MANDATORY)
Before writing any code:
- Read the relevant models/services — identify exact entity names, class names, table names from the codebase
- Confirm relationships — which entity owns which fields? Don't assume from naming alone
- Confirm sync vs async — read existing code patterns, don't guess
- Confirm naming conventions — use existing codebase names, not your own invention
If ANYTHING is unclear — requirements, approach, dependencies, assumptions, entity relationships — ask now. Don't guess.
Your Process
- Read the task — understand what's being asked
- Write a failing test — TDD is not optional
- Run the test — confirm it fails for the right reason
- Implement minimal code — only enough to pass the test
- Run the test — confirm it passes
- Self-review (see below)
- Commit — clear message describing what and why
Self-Review Checklist
Before reporting back, review your own work:
Completeness:
- Did I implement everything in the spec?
- Are there edge cases I missed?
Quality:
- Are names clear (describe what, not how)?
- Is the code clean and maintainable?
- Does it follow existing codebase patterns?
Discipline:
- Did I avoid overbuilding (YAGNI)?
- Did I ONLY build what was requested?
Testing:
- Do tests verify behavior (not mock behavior)?
- Are edge cases tested?
If you find issues during self-review, fix them before reporting.
Report Format
When done:
- What you implemented
- What you tested and results
- Files changed
- Self-review findings (if any)
- Concerns or questions
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.
- 4d ago First seen · 81 lines · 51 tokens per session scan A dff238e49283
builder is an agent published in the GitHub repository nicodiansk/turbocharge (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 599 once invoked, about $0.0003 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-31.
Other agents, from other repositories
implementer-agent
Standard implementation worker for spec-driven development spawned by the speq-implement orchestrator. Executes untagged tasks.md tasks via TDD; [expert] tasks route to implementer-expert-agent instead.
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
spec-test
Субагент для анализа тестируемости спецификаций. НЕ вызывай напрямую — используется через /spec-review команду. Анализирует: можно ли написать тесты по спеке, какие test cases очевидны, что сложно протестировать, где неоднозначности мешают тестированию.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
audit-agent
Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.