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/theam/claude-dev-kit/work-storynpx skills add theam/claude-dev-kit --skill work-storygit clone --depth 1 https://github.com/theam/claude-dev-kitWrote 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/theam/claude-dev-kit/work-story)<a href="https://agentmods.dev/skills/theam/claude-dev-kit/work-story"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/work-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 | $0.00057 | $0.01168 |
| Opus 5 | $0.00028 | $0.00584 |
| Sonnet 5 | $0.00011 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
work-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 today.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Story (orchestration)
You are the story orchestrator. Input: an issue key from the team's tracker. Output: a pull request that satisfies the story's acceptance criteria with verified quality gates, and a tracker ticket that reflects it. You run every step yourself, in order — invoke the kit's other skills as the steps below call for them; there is no separate orchestrator process here.
If no issue reference is given, ask for one — don't guess. Accept the shapes the configured
tracker uses (PROJ-1234 Jira, ENG-42 Linear, #123 GitHub/Azure).
Stack-agnostic. Carry no assumptions about language, framework, or test runner. Read the
repo's AGENTS.md / CLAUDE.md and .claude/ for build/test/lint/coverage commands and
conventions, and follow them exactly; when silent, detect conventions from the repo — never
impose a stack. The always-on rules in instructions/secure-coding.md and
instructions/testing-standards.md bind every step.
1. Context
- If
.claude/dev-kit.jsonis missing, rundev-kit-setupfirst (one-time bootstrap: tracker, project/team, field IDs). - Run
issue-fetchfor the ticket and show the summary. - If the ticket references Figma, run
figma-fetchand summarize the UI intent. - Read the repo's project instructions and load the baseline stack profile
(
instructions/stacks/<id>.mdfor thestacksin.claude/dev-kit.json); the repo's own instructions always win, the profile fills gaps.
2. Plan — WAIT FOR APPROVAL
Validate assumptions against the running product when feasible (boot the app / exercise the flow) before writing the plan. Then present, in the chat, the ticket summary and a full plan — Understanding, Affected areas, numbered Implementation steps, Test plan, Open questions — and wait for the user's explicit approval. Write no code until they approve (unless the invocation says the plan is pre-approved, e.g. an automated run).
3. Implement
- Follow the repo's conventions and architecture. Keep the diff scoped to the story — no opportunistic refactors.
- Update every side of any changed contract (payload/route/enum/schema/validation) together.
- For user-facing frontend work, write accessible markup as you go (semantic HTML, labels,
alt, keyboard/focus) — cheaper than fixing it at review.
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.
- today Changed · +6 lines fb266a6dc311
- 4d ago First seen · 74 lines · 57 tokens per session scan A 6dad72c896f3
work-story is a skill published in the GitHub repository theam/claude-dev-kit (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,168 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-08-30.
Other skills, from other repositories
triage-task
Reads a ticket from Jira or Azure DevOps and writes .workflow/ /triage.json. Use when asked what to work on, to pick up a ticket by key, or to understand its description, comments and blocking links.
pm-config
Initialize or reconfigure MDPM (ID prefix, task directories, sync preferences).
pm-sync-jira
Sync task state with Jira via MCP (optional, graceful degradation).
pm-plan
Break a feature or epic into 3-8 scoped tasks with dependency mapping.
pm-sync-wrike
Sync task state with Wrike via MCP (optional, graceful degradation).
pm-board
Print the command to launch the local kanban board (does not start a background server).