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/cpliakas/claude-code-engineering-leaders/write-epicnpx skills add cpliakas/claude-code-engineering-leaders --skill write-epicgit clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/write-epic)<a href="https://agentmods.dev/skills/cpliakas/claude-code-engineering-leaders/write-epic"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/write-epic.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.00021 | $0.00699 |
| Opus 5 | $0.00010 | $0.00349 |
| Sonnet 5 | $0.00004 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
write-epic 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 5d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Epic
Write a complete epic specification with scope, success criteria, and scope boundaries.
Input
$ARGUMENTS = epic title and high-level description of the initiative.
Process
1. Handle Missing Input
If $ARGUMENTS is empty or contains no actionable description, prompt the user for the minimum information needed:
- Epic title — a concise name for the initiative.
- Brief description — what problem or opportunity does this epic address?
Do not proceed until the user has provided at least a title and a one-sentence description.
2. Gather Context
- Read the project's CLAUDE.md for architecture, conventions, and strategic context
- Scan for a roadmap or backlog file if one exists (Glob for roadmap*, backlog*, TODO*)
- Identify existing work that this epic relates to or depends on
3. Define the Epic
Title: Scoped and outcome-oriented.
- Good: "User Authentication — Email and OAuth Login"
- Bad: "Auth stuff" or "Sprint 4 work"
Epic specification body:
## Problem Statement
[1-2 sentences: What problem does this solve? Who is affected? What happens if
we do nothing?]
## Desired Outcome
[1-2 sentences: What does success look like when this epic is complete?]
## Success Metrics
- [Measurable indicator 1]
- [Measurable indicator 2]
## Scope
**In scope:**
- [Capability or deliverable that IS included]
**Out of scope:**
- [Capability explicitly excluded — prevents scope creep]
**Non-goals:**
- [Things this epic intentionally does NOT try to achieve]
## Dependencies and Risks
- **Depends on**: [other epics, services, decisions, or infrastructure]
- **Blocks**: [what downstream work is waiting on this epic]
- **Risks**: [technical unknowns, external dependencies, capacity concerns]
4. Validate the Epic
Check the overall epic before finalizing:
- Right-sized: spans multiple sprints but delivers value each sprint
- Strategically aligned: connects to a clear user or business need
- Measurable: success metrics are specific and verifiable
- Scoped: in-scope and out-of-scope are explicit — no ambiguity about boundaries
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.
- 5d ago First seen · 119 lines · 21 tokens per session scan A 867d97102deb
write-epic is a skill published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 13d ago), licensed MIT. It adds 21 tokens to every session and 699 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…