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 agentmods add skills/cenconq25/claude-code-app-studio/create-epicsnpx skills add cenconq25/claude-code-app-studio --skill create-epicsgit 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-epics)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/create-epics"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/create-epics.svg" alt="Measured on agentmods" 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 | $0.00066 | $0.01903 |
| Opus 5 | $0.00033 | $0.00951 |
| Sonnet 5 | $0.00013 | $0.00381 |
| Haiku 4.5 | $0.00007 | $0.00190 |
Grade A, and why
create-epics 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 yesterday.
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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Epics
An epic is the unit between architecture and stories. It groups related stories under a shared system or module, declares the governing ADRs, and surfaces the framework risk so the engineer knows what to verify before coding.
Output: production/epics/<epic-slug>/EPIC.md (one file per epic)
Purpose / When to Run
Run when:
/architecture-reviewreturned PASS or CONCERNS (not FAIL)/create-control-manifestis written and dated- The team is ready to plan stories
Do not decompose into stories here — /create-stories <epic-slug> does that.
Inputs
- All
design/prd/*.md - All Accepted
docs/architecture/ADR-*.md docs/architecture/architecture.mddocs/architecture/control-manifest.mddocs/framework-reference/<framework>/- Optional
<system-name>argument: only generate the epic for this system
Outputs
production/epics/<epic-slug>/EPIC.md— one per system in scope
Phase 1: Pre-checks
- Confirm at least one Accepted ADR exists
- Confirm
docs/architecture/control-manifest.mdexists and read its Manifest Version - If a previous epic for the same system exists, ask:
Refresh,Replace,Cancel
If <system-name> argument given, scope to that system; else, do all in-scope MVP systems from the systems index.
Phase 2: Read All Context
Read the inputs in full. Hold:
- Each PRD's Detailed Requirements (all TR-IDs)
- Each PRD's Acceptance Criteria
- Each ADR's PRD Requirements Addressed table
- Architecture Section 3 (Layers) and Section 20 (Required ADRs)
- Control manifest Required/Forbidden/Guardrail by layer
Phase 3: Group TR-IDs into Epics
The mapping rule: one epic per system, with stories living inside.
Special cases:
- If a system is huge (>30 TR-IDs), split into 2-3 sub-epics (e.g., "Auth — Sign-in", "Auth — Account & Recovery")
- Foundation systems (state, navigation, networking) become epics if they need any user-visible scaffolding work
- Cross-cutting concerns (analytics, error reporting) become their own epics if they have ≥3 TR-IDs of dedicated work
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.
- yesterday First seen · 229 lines · 66 tokens per session scan A 8c6e18cf1279
create-epics is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 66 tokens to every session and 1,903 once invoked, about $0.0003 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
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.