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 tobihagemann/turbo --skill implement-plangit clone --depth 1 https://github.com/tobihagemann/turboWrote 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/tobihagemann/turbo/implement-plan)<a href="https://agentmods.dev/skills/tobihagemann/turbo/implement-plan"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/implement-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/tobihagemann/turbo/implement-plan"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/implement-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 12 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00048 | $0.01371 |
| Opus 5.5 | $0.00019 | $0.00548 |
| Sonnet 5.5 | $0.00010 | $0.00274 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
implement-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 3d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Plan
Execute an implementation plan file.
Task Tracking
At the start, use TaskCreate to create a task for each step:
- Resolve and read the plan file
- Read context files
- Run
/implementskill - Update plan status
Step 1: Resolve and Read the Plan File
Determine which plan file to implement using these rules in order:
- Explicit path — If an absolute or relative path was passed and that file exists, use it
- Explicit slug — If a slug was passed (e.g.,
add-image-cache), resolve to.turbo/plans/<slug>.mdif that file exists - Single file — Glob
.turbo/plans/*.md. If exactly one plan exists, use it - Most recent — If multiple plans exist, use the most recently modified
- Legacy fallback — If
.turbo/plans/does not exist but.turbo/plan.mdexists, use it - Nothing found — If no rule above resolved to an existing file, tell the user to run
/turbo:planand stop. When a slug or path was passed but no file matched it, say which one was tried
If multiple plans exist and the most-recent choice is non-obvious (e.g., several plans were modified within the same minute), use AskUserQuestion to let the user pick from the candidates.
State the resolved plan path before continuing, then read the file.
Unless an explicit path or slug was passed, confirm the resolved plan still describes work that remains to be done:
- Already implemented — the frontmatter
status:isdone - Waiting on a gate — the plan's Context states a gate that must pass before its work can start
When you check whether a gate has passed, check each condition it names at its source of record, such as the remote's tags for another repository's release, rather than a local copy.
When a signal fires, output it as text. Then use AskUserQuestion to offer:
- Implement anyway — the marker is stale, or the gate has passed
- Pick another plan — resolve to a different file under
.turbo/plans/, then confirm that plan against these same signals - Leave it unimplemented — the plan needs revising first, or its gate has not passed
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.
- 3d ago Changed · -44 tokens per session 713b5dfa3c32
- 4d ago Changed 13bac0d9154e
- 29d ago Changed · +2 lines 82af2b007309
- 1mo ago Changed · +9 lines 4de1f3bd72fb
- 1mo ago Changed d0bd1462b9d6
- 1mo ago Changed · +1 lines da69fd39c104
- 1mo ago Changed · +2 lines 60db71af0e1d
- 1mo ago Changed · +2 lines 1287d4488d30
- 2mo ago First seen · 68 lines · 92 tokens per session scan A 62c3b767cb03
implement-plan is a skill published in the GitHub repository tobihagemann/turbo (420 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,371 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-30.
implement-plan compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| implement-plantobihagemann/turbo | Skill | 420 | today | MIT | A | 48 | Claude Code |
| offensive-c2-frameworksSnailSploit/Claude-Red | Skill | 11k | yesterday | MIT | A | 250 | Claude Code, Codex |
| offensive-crypto-attacksSnailSploit/Claude-Red | Skill | 11k | yesterday | MIT | A | 261 | Claude Code, Codex |
| offensive-parameter-pollutionSnailSploit/Claude-Red | Skill | 11k | yesterday | MIT | A | 0 | Claude Code, Codex |
| offensive-z-waveSnailSploit/Claude-Red | Skill | 11k | yesterday | MIT | A | 113 | Claude Code, Codex |
| fiscalisteromainsimon/paperasse | Skill | 2.6k | today | MIT | A | 306 | Claude Code |
| comptableromainsimon/paperasse | Skill | 2.6k | today | MIT | A | 248 | Claude Code |