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 skills add nicodiansk/turbocharge --skill plangit 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/skills/nicodiansk/turbocharge/plan)<a href="https://agentmods.dev/skills/nicodiansk/turbocharge/plan"><img src="https://agentmods.dev/badge/skills/nicodiansk/turbocharge/plan/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/skills/nicodiansk/turbocharge/plan"><img src="https://agentmods.dev/badge/skills/nicodiansk/turbocharge/plan.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.00038 | $0.01464 |
| Opus 5.5 | $0.00015 | $0.00586 |
| Sonnet 5.5 | $0.00008 | $0.00293 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
plan 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 10d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Implementation Plan
Read the requirements at $ARGUMENTS and create a lean implementation plan.
Plan Document Header
Every plan MUST start with:
# [Feature Name] Implementation Plan
**Goal:** [One sentence]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies]
## Lanes
| Lane | Owns files | Tasks | After | Executor | Effort |
|------|-----------|-------|-------|----------|--------|
| [name] | `src/full/path.py`, `tests/full/test_path.py` | 1–3 | — | inline | — |
| [name] | `src/other/module.py`, `tests/other/test_module.py` | 4–6 | [lane] | builder | medium |
## Review Focus
- [input or condition the spec implies but never names] → [what a reasonable user expects] (pinned: Task N)
Lanes let /turbocharge:build run independent work side by side and skip a builder spawn for mechanical work:
- A lane owns a set of files, listed as full repo-relative paths — build diffs and reviews each lane by them. No file belongs to two lanes — test files included.
- Tasks inside a lane run in order.
Afternames lanes that must finish first; lanes with noAfterpath between them may overlap. - Executor is a hint:
inlinefor mechanical lanes (content edits, exact text given, ≤3 tasks) that the main session applies directly;builderfor real logic or lanes with judgment calls, run by one builder for the whole lane. - Effort (
low/medium/high) applies to builder lanes; use—for inline. - A small plan can be a single lane.
Review Focus names up to 5 input classes or failure modes the spec implies but never names, and that no task's test would otherwise exercise: the empty list, the duplicate, the field with a comma, the rerun. One line each, most likely first: the input, then what a reasonable user expects. The spec says what the software must do, not everything it will meet; its silence on an input is not permission for that input to break the program. The task that owns the code gets a test assertion that pins each line, and the line names that task. If nothing is implied, write None found — <why>.
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.
- 10d ago Changed · +2 lines b5419d8bbe0a
- 12d ago Changed · +12 lines 31e2a45c468d
- 13d ago Changed · +1 lines · +5 tokens per session 042ae30ecc46
- 1mo ago First seen · 82 lines · 33 tokens per session scan A f2399a6b814b
plan is a skill published in the GitHub repository nicodiansk/turbocharge (3 stars, last pushed 7d ago), licensed MIT. It adds 38 tokens to every session and 1,464 once invoked, about $0.0002 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-31.
Other skills, from other repositories
ccs-align
Run the CCS Align seat's hourly breathing cycle — prove the local claude-mem worker is healthy, pull needle observations through search → timeline → getobservations, land them in a seat-owned middle cache via atomic grab → append → filter exclude-marks → replace, manage exclude marks, and walk house → project → seat…
design-is
Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design…
Agent Cost Report
Believable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json…
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
request-progress
Group recent conversations into overall requests, review each one's progress from memory, link each to the owner goals it serves, and write the build story, so My Work shows progress meters, shipping velocity and learned working preferences. Use when asked to "group requests", "group by overall request", "review…
smart-explore
Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.