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 storygit 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/story)<a href="https://agentmods.dev/skills/nicodiansk/turbocharge/story"><img src="https://agentmods.dev/badge/skills/nicodiansk/turbocharge/story/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/story"><img src="https://agentmods.dev/badge/skills/nicodiansk/turbocharge/story.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.00037 | $0.00990 |
| Opus 5 | $0.00018 | $0.00495 |
| Sonnet 5 | $0.00007 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
story 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 11d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Breakdown
Transform requirements into INVEST-compliant user stories with testable acceptance criteria.
Announce: "Using story breakdown to create implementable stories."
The Iron Law
NO STORY WITHOUT ACCEPTANCE CRITERIA
Every story must have testable acceptance criteria before implementation.
No exceptions:
- Don't start work without criteria
- Don't assume "obvious" criteria
- Don't defer criteria to "later"
- Later never comes
INVEST Criteria
Every story MUST pass:
| Criterion | Question | Failure Symptom |
|---|---|---|
| Independent | Can this ship without other stories? | "We need to do X first" |
| Negotiable | Can scope be discussed? | "It has to be exactly this" |
| Valuable | Does user/business care? | "It's technical debt" |
| Estimable | Can team size it? | "No idea how long" |
| Small | Fits in one iteration? | "It's a 2-week story" |
| Testable | Can we verify done? | "We'll know when we see it" |
Failing any criterion = story needs work.
Epic Template
# Epic: [Name]
## Problem Statement
[What problem does this solve? Who has this problem?]
## Success Metrics
- [Measurable outcome 1]
- [Measurable outcome 2]
## Scope
### In Scope
- [Feature/capability]
### Out of Scope
- [Explicitly excluded]
## Stories
1. [Story 1 title]
2. [Story 2 title]
## Dependencies
- [External dependencies]
## Risks
- [Risk]: [Mitigation]
Story Template
# Story: [Title]
**As a** [role/persona],
**I want** [capability/feature],
**So that** [benefit/value].
## Acceptance Criteria
### Criterion 1: [Name]
**Given** [precondition]
**When** [action]
**Then** [expected result]
### Criterion 2: [Name]
**Given** [precondition]
**When** [action]
**Then** [expected result]
## Technical Notes
- [Implementation consideration]
## Story Points: [1/2/3/5/8]
Breakdown Process
Phase 1: Understand the Epic
- Identify the user/persona
- State the core problem
- Define success metrics
- List what's explicitly OUT of scope
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.
- 11d ago First seen · 158 lines · 37 tokens per session scan A 5070906acfac
story is a skill published in the GitHub repository nicodiansk/turbocharge (2 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 990 once invoked, about $0.0002 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 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…
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"…
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.
wowerpoint
Turn one document into a kawaii NotebookLM slide-deck PDF. Use for "wowerpoint this", "make a deck about ", "turn this report into slides", or any request to render a single document as shareable narrative slides.
standup
Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.