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 commands/theam/claude-dev-kit/launch-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/commands/theam/claude-dev-kit/launch-story)<a href="https://agentmods.dev/commands/theam/claude-dev-kit/launch-story"><img src="https://agentmods.dev/badge/commands/theam/claude-dev-kit/launch-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.00034 | $0.00339 |
| Opus 5 | $0.00017 | $0.00169 |
| Sonnet 5 | $0.00007 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
launch-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 4d 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.
What it actually says
Prepare a dedicated workspace for the story given in the arguments: $ARGUMENTS
You are the launcher — you do NOT work the story yourself. Steps:
-
Validate the issue reference (the shape your tracker uses, e.g.
PROJ-1234,ENG-42,#123); if missing, ask — do not guess. -
Create the worktree (from the repo root, using a short slug from the issue key):
git worktree add ../<repo-name>-<slug> -b feat/<slug>-storywhere
<slug>is the issue key made branch-safe (strip a leading#, replace anything non-alphanumeric with-). If the worktree or branch already exists, reuse it and say so. -
Open the window:
code <worktree-path>. If thecodeCLI is unavailable, tell the user to open the folder manually. -
Report the worktree path and branch, and give the user the exact next step to run in the NEW window's Claude session, ready to copy:
/fullstack-dev-kit:work-story <TICKET-KEY>Also remind them: when the PR is merged, remove the worktree with
git worktree remove <path>.
Do not start the pipeline in THIS conversation — the new window owns the story end to end.
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.
- 4d ago First seen · 26 lines · 34 tokens per session scan A 866767cf76bc
launch-story is a command published in the GitHub repository theam/claude-dev-kit (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 339 once invoked, about $0.0002 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 commands, from other repositories
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.
check-dev
Type-check a Z specification with fuzz.