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 create-storiesgit 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/create-stories)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/create-stories"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/create-stories/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/create-stories"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/create-stories.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.00067 | $0.02190 |
| Opus 5.5 | $0.00027 | $0.00876 |
| Sonnet 5.5 | $0.00013 | $0.00438 |
| Haiku 4.5 | $0.00007 | $0.00219 |
Grade A, and why
create-stories 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 1mo 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Stories
A story is a single implementable behavior — small enough for one focused session, traceable to a TR-ID and an ADR. This skill produces story files that /dev-story and /story-readiness (in the second skill set) will read.
Output: production/epics/<epic-slug>/story-NNN-<slug>.md
Phase 1: Parse Argument
Resolve review mode (--review or production/review-mode.txt, default lean).
Acceptable arg forms:
<epic-slug>(e.g.,auth-sign-in)- Full path to
EPIC.md - Empty — list available epics and ask which
If no epics exist, stop and recommend /create-epics.
Phase 2: Load the Epic & Its World
Read in full:
production/epics/<slug>/EPIC.md- The PRD listed in EPIC Section 2
- Each ADR listed in EPIC Section 3
docs/architecture/control-manifest.md(note Manifest Version)
ADR existence check: confirm every governing ADR file exists on disk. If any is missing, halt:
"Epic references ADR-NNNN but
docs/architecture/ADR-NNNN-...mddoes not exist. Cannot decompose stories until that file is in place. Run/architecture-decisionto create it."
Report: "Loaded epic , PRD , governing ADRs, manifest version ."
Phase 3: Classify Story Types
Mobile-app story types:
| Type | Use when criteria reference… |
|---|---|
| Logic | Calculations, validation rules, state transitions, business decisions |
| Integration | Two systems interacting (e.g., auth → push token registration) |
| Visual / Feel | Animation, transitions, motion, "feels responsive", micro-interactions |
| UI | Static screens, menus, settings forms, modals |
| Config / Data | Token / threshold / copy changes only — no new code logic |
| Platform | Framework-specific glue (push setup, biometrics, IAP plumbing) |
Mixed stories: pick the type that carries the highest implementation risk. The type determines the test-evidence requirement.
Phase 4: Decompose
For each PRD Acceptance Criterion in scope:
- Group related criteria that share a single implementation
- Each group = one story
- Order: Foundation behavior → Core → Edge cases → UI polish
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.
- 1mo ago First seen · 268 lines · 67 tokens per session scan A 671c462e2d8c
create-stories is a skill published in the GitHub repository cenconq25/claude-code-app-studio (42 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 2,190 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.