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 cenconq25/claude-code-app-studio --skill story-donegit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/story-done)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/story-done"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/story-done/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/cenconq25/claude-code-app-studio/story-done"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/story-done.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.00048 | $0.01648 |
| Opus 5 | $0.00024 | $0.00824 |
| Sonnet 5 | $0.00010 | $0.00330 |
| Haiku 4.5 | $0.00005 | $0.00165 |
Grade A, and why
story-done 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 6d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Done
The closing gate of the per-story loop. Reads the story, audits each acceptance criterion against the actual implementation, ensures evidence is in place, prompts a code review if one is missing, then transitions Status to Complete and points the user at the next ready story.
Phase 1: Resolve the Story
If a path is supplied, use it. Otherwise consult
production/session-state/active.md for an active story, or glob
production/epics/**/*.md and ask the user which one.
Stop and warn if the story file does not exist.
Phase 2: Read Story + Implementation Files
Pull these from the story:
- Story ID, Title, Layer, Type
- TR-ID and Governing ADR
- Acceptance Criteria (every checkbox)
- Implementation Notes
- Test Evidence path
- Out of Scope list
- Status (must be
In ProgressorIn Review; if alreadyComplete, ask the user whether to re-verify)
Glob the most recent edits to src/ to find files modified for this story.
Cross-reference with the session state file. Read each modified file.
If a Test Evidence path is specified, read the test file. If absent for a Logic or Integration story, this is a hard blocker (see Phase 5).
Phase 3: Verify Each Acceptance Criterion
Walk every AC checkbox in order. For each:
| Story Type | Verification method |
|---|---|
| Logic | Locate test function(s) covering the AC; confirm assertions match the AC text; confirm CI run was green. |
| Integration | Locate integration test or documented playtest evidence; confirm the cross-system interaction is exercised. |
| Visual/Feel | Ask the user via AskUserQuestion for sign-off; require an attached screenshot or screen recording in production/qa/evidence/. |
| UI | Ask the user to walk through the flow on a device; require an evidence note or attached screenshot. |
| Config/Data | Confirm a smoke check report exists (production/qa/smoke-[date].md) and the values shipped match the story. |
Mark each AC one of: VERIFIED, DEFERRED (Visual/Feel awaiting user
confirmation), MISSING EVIDENCE, or FAILED.
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.
- 6d ago First seen · 212 lines · 48 tokens per session scan A 432a563c4a09
story-done is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 1,648 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-09-03.
Other skills, from other repositories
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
tech-debt
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.