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 uthumany/uthy-legacy-os --skill user-story-writergit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/user-story-writer)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/user-story-writer"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/user-story-writer/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/skills/uthumany/uthy-legacy-os/user-story-writer"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/user-story-writer.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.00027 | $0.01005 |
| Opus 5 | $0.00014 | $0.00502 |
| Sonnet 5 | $0.00005 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
user-story-writer 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 12d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Story Writer
Overview
User stories are the atomic unit of product work. A well-written story describes what a user needs, why they need it, and how we'll know it works — small enough to ship in a sprint, clear enough that no one needs to ask "what did they mean?" This skill follows Mike Cohn's format with INVEST criteria.
When to Use
- Breaking features into sprint-sized pieces of work
- Handing requirements off to engineering and QA
- Building and maintaining a product backlog
- Writing stories for a specific epic or initiative
- Don't use for: technical infrastructure work (use tasks, not stories), bug fixes (write a bug report with reproduction steps), or system designs
Instructions
1. Follow the User Story Format
**As a** [type of user],
**I want** [goal or action],
**So that** [reason or benefit].
- Who: A specific user role (not "user")
- What: An action or goal, not a UI detail
- Why: The benefit — this is the most important part
Examples:
- ❌ "As a user, I want a button to export to CSV" (focuses on UI)
- ✅ "As a marketing manager, I want to download campaign reports so I can share them with my team."
2. Apply INVEST Criteria
- Independent: Can it be shipped alone?
- Negotiable: Is there room for discussion on implementation?
- Valuable: Does it deliver value to the user?
- Estimable: Can the team estimate effort?
- Small: Can it be completed in a sprint?
- Testable: Can QA verify it's done?
If a story fails any INVEST check, split or rewrite it.
3. Add Acceptance Criteria
Write 3-7 criteria using Given/When/Then format (see acceptance-criteria skill).
4. Add Context
For each story, include:
- Design link: Figma or mockup reference
- Technical notes: Architecture decisions, API contracts
- Dependencies: Other stories or tasks that must come first
- Definition of Done: Team-specific completion checklist
5. Size and Prioritize
- Estimate effort using your team's method (t-shirt sizes, points, hours)
- Prioritize within the epic using RICE or value-effort
- Order by dependency and value
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.
- 12d ago First seen · 107 lines · 27 tokens per session scan A 5d34cea176b8
user-story-writer is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 1,005 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…