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.
git clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/user-story-gen)<a href="https://agentmods.dev/commands/dokkabei97/forged-claude-code/user-story-gen"><img src="https://agentmods.dev/badge/commands/dokkabei97/forged-claude-code/user-story-gen/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/dokkabei97/forged-claude-code/user-story-gen"><img src="https://agentmods.dev/badge/commands/dokkabei97/forged-claude-code/user-story-gen.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.01147 |
| Opus 5.5 | $0.00008 | $0.00459 |
| Sonnet 5.5 | $0.00004 | $0.00229 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
user-story-gen 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 1mo 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/user-story-gen - User Story Generator
Triggers
- When a PRD or feature description needs to be broken into implementable stories
- When planning sprint backlog items
- When acceptance criteria need to be formalized
Usage
/user-story-gen [feature description or PRD path]
/user-story-gen --from prd.md
/user-story-gen "Users can upload profile photos"
Behavioral Flow
Phase 1: Input Analysis
Analyze the input to understand the feature scope.
If file path provided:
Read the PRD/spec file
Extract: Problem statement, scope items, user flows
If text description provided:
Parse the feature description
Identify: User types, actions, goals
Phase 2: Identify User Types
Extract all distinct user types/personas from the input:
- Primary user (the main beneficiary)
- Secondary users (admin, support, etc.)
- System actors (scheduled jobs, webhooks, etc.)
Phase 3: Generate User Stories
For each scope item, generate stories following INVEST principles:
| Principle | Check |
|---|---|
| Independent | Can be developed without other stories |
| Negotiable | Not a contract, details can change |
| Valuable | Delivers value to user or business |
| Estimable | Team can estimate effort |
| Small | Fits in one sprint (ideally 1-3 days) |
| Testable | Clear pass/fail criteria |
Story Format:
### [STORY-ID] [Short Title]
> As a **[user type]**,
> I want to **[action/capability]**,
> so that **[benefit/value]**.
**Acceptance Criteria:**
- [ ] Given [precondition], when [action], then [expected result]
- [ ] Given [precondition], when [action], then [expected result]
- [ ] Given [edge case], when [action], then [expected result]
**Notes:**
- [Implementation hints or constraints]
- [Dependencies on other stories]
**Size:** S / M / L
**Priority:** P0 (must) / P1 (should) / P2 (could)
Phase 4: Story Splitting
If a story is too large (estimated > 3 days), split it using these patterns:
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.
- 1mo ago First seen · 174 lines · 20 tokens per session scan A 91b5c86e6920
user-story-gen is a command published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 8mo ago), licensed MIT. It adds 20 tokens to every session and 1,147 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
status
Display project status, active tracks, and next actions.
amend-plan
Plan Amend - Discuss and apply amendments to a plan.json implementation plan.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
triage
Process the user-feedback queue — triage new reports, keep the status mirror honest, and (at release time only) send the shipped emails.
audit
Audit closed tickets for regressions against today's code (unchanged, evolved, implemented wrong, not implemented), plus duplicate and groupable open ones.