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 implementgit 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)<a href="https://agentmods.dev/skills/tobihagemann/turbo/implement"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/implement/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"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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.
- medium Excessive Agency · line 40 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00046 | $0.02085 |
| Opus 5.5 | $0.00018 | $0.00834 |
| Sonnet 5.5 | $0.00009 | $0.00417 |
| Haiku 4.5 | $0.00005 | $0.00209 |
Grade A, and why
implement 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement
Standard implementation flow: load style rules, make the change, run post-implementation QA.
Task Tracking
At the start, use TaskCreate to create a task for each step:
- Run
/code-styleskill - Load task-specific skills
- Make the change
- Run verification
- Run
/smoke-testskill for UI/UX changes - Run
/previewskill for UI/UX changes - Post-implementation QA
Step 1: Run /code-style Skill
Run the /code-style skill to load existence, reuse, mirror, and symmetry rules before editing.
Step 2: Load Task-Specific Skills
Scan the work for types that match available skills, matching against the richest context available: a plan's Implementation Steps if a plan is in conversation context, otherwise the user request, a prior skill's task description, or an improvement entry. For each unambiguous match, run the skill via the Skill tool. For example, if the work includes "add a Drizzle migration" and a skill exists whose triggers reference Drizzle migrations, load it. If a work type has no matching skill trigger, do not load a generic skill.
If unsure, do not load.
Step 3: Make the Change
Unless one subagent per step was settled on for a plan that governs the work, apply the change described by the current context — the user request, a prior skill's task description, or an improvement entry. Keep the edit scoped to what the context describes.
When the fix changes how a value is constructed, grep for every other site that constructs it and fix the ones carrying the same defect; treat these siblings as part of the same change. If the scope balloons beyond what the context specified, stop and confirm scope before continuing.
When a plan governs the work and one subagent per step was settled on for it, the Implementation Steps go to subagents, and this session reviews what each one returns. Use TaskCreate to create a task for each Implementation Step, then take them in order, one at a time.
Before each spawn, capture git status --short and run git stash create, which snapshots the working tree without changing it and prints nothing when the tree is clean.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +1 lines 223f65571ef0
- 3d ago Changed · -23 tokens per session d29e87a67203
- 4d ago Changed d223002ed5c2
- 1mo ago Changed · +2 lines 18b392914f0e
- 1mo ago Changed · +2 lines b3fef33a85e4
- 1mo ago Changed · +22 lines 1a78e1fe4c75
- 1mo ago Changed · +4 lines 1b93844e969c
- 2mo ago Changed · +2 lines 980b7a28ffb5
- 2mo ago Changed ae130052d69f
- 2mo ago First seen · 68 lines · 69 tokens per session scan A 7e0f904cd827
implement is a skill published in the GitHub repository tobihagemann/turbo (420 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 2,085 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 compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| implementtobihagemann/turbo | Skill | 420 | today | MIT | A | 46 | 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 |