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 cpliakas/claude-code-engineering-leaders --skill write-storygit 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-story)<a href="https://agentmods.dev/skills/cpliakas/claude-code-engineering-leaders/write-story"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/write-story.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.1 | $0.00017 | $0.02958 |
| Opus 5 | $0.00009 | $0.01479 |
| Sonnet 5 | $0.00003 | $0.00592 |
| Haiku 4.5 | $0.00002 | $0.00296 |
Grade A, and why
write-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 7d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Story
Write a complete, high-quality user story with INVEST validation.
Input
$ARGUMENTS = description of the feature, requirement, or problem to solve.
Process
1. Gather Context
- Read the project's CLAUDE.md for architecture, conventions, and domain language
- Scan for a roadmap or backlog file if one exists (Glob for roadmap*, backlog*, TODO*)
- Understand the domain well enough to write specific, testable criteria
Readiness assessment:
- If the story has hard blockers on unstarted work (entire epics or phases that have not begun), classify readiness as
backlogand skip to the Backlog-Tier Output section at the end of this skill - If dependencies are complete or actively in-progress, classify readiness as
sprint-readyand continue the full process below
Detailed specification should happen at pull time, not envisioning time. Stories deep in the backlog will change as the project evolves — investing in full acceptance criteria and technical notes for work that is months away produces waste. A lightweight backlog entry captures intent and scope; the full story gets written when the team is ready to start.
2. Assess Context Sufficiency
Gate: If readiness is
backlog, skip to the Backlog-Tier Output section.
Before drafting, evaluate whether the input provides enough detail across four dimensions:
| Dimension | Sufficient when | Prompt if underspecified |
|---|---|---|
| Persona | A specific role or actor is named or clearly implied | "Who is the primary user or actor for this requirement?" |
| Observable behavior | The desired system behavior is concrete enough to demonstrate | "What should the system do — what would a user see or experience?" |
| Benefit / motivation | A reason or outcome beyond restating the capability is present | "Why does this matter — what problem does it solve or what outcome does it enable?" |
| Scope boundaries | At least a rough sense of what is in and out of scope is present | "What is explicitly out of scope or deferred for this 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.
- 7d ago First seen · 264 lines · 17 tokens per session scan A f2c71d87b2cf
write-story is a skill published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 16d ago), licensed MIT. It adds 17 tokens to every session and 2,958 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
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…
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.