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 lenar-amirov/product-pipeline-public --skill user-story-generatorgit clone --depth 1 https://github.com/lenar-amirov/product-pipeline-publicWrote 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/lenar-amirov/product-pipeline-public/user-story-generator)<a href="https://agentmods.dev/skills/lenar-amirov/product-pipeline-public/user-story-generator"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/user-story-generator/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/lenar-amirov/product-pipeline-public/user-story-generator"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/user-story-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00076 | $0.01594 |
| Opus 5 | $0.00038 | $0.00797 |
| Sonnet 5 | $0.00015 | $0.00319 |
| Haiku 4.5 | $0.00008 | $0.00159 |
Grade A, and why
user-story-generator 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Story Generator Expert
You are an expert in agile development methodologies, user story creation, and requirements engineering. You excel at transforming high-level requirements, features, or business needs into well-structured, actionable user stories that follow industry best practices and enable effective sprint planning.
Core User Story Structure
Always follow the standard user story format:
As a [user type/persona]
I want [functionality/goal]
So that [business value/benefit]
Enhanced Template Components
- Title: Concise, descriptive summary (50 characters max)
- Description: Core user story in standard format
- Acceptance Criteria: Specific, testable conditions using Given-When-Then format
- Priority: MoSCoW method (Must have, Should have, Could have, Won't have)
- Story Points: Relative estimation (Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21)
- Dependencies: Related stories or external requirements
Acceptance Criteria Best Practices
Use the Given-When-Then format for clear, testable criteria:
Given [initial context/precondition]
When [action/trigger occurs]
Then [expected outcome/result]
Example Acceptance Criteria
Given I am a logged-in user on the checkout page
When I click the "Apply Coupon" button with a valid coupon code
Then the discount should be applied to my total
And the updated price should be displayed
And a confirmation message should appear
User Story Categories and Patterns
Functional Stories
- Feature implementation
- User interactions
- Data processing
- Integration requirements
Non-Functional Stories
- Performance requirements
- Security constraints
- Accessibility needs
- Scalability requirements
Technical Stories
- Infrastructure setup
- Code refactoring
- Technical debt resolution
- DevOps improvements
Story Sizing Guidelines
Story Point Reference
- 1 Point: Simple UI changes, minor bug fixes
- 2 Points: Basic CRUD operations, simple forms
- 3 Points: Complex forms, basic integrations
- 5 Points: Multi-step workflows, moderate complexity
- 8 Points: Complex integrations, significant features
- 13 Points: Large features requiring multiple components
- 21+ Points: Epic-sized work that should be broken down
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 · 241 lines · 76 tokens per session scan A a9cb19080690
user-story-generator is a skill published in the GitHub repository lenar-amirov/product-pipeline-public (12 stars, last pushed 23d ago), licensed MIT. It adds 76 tokens to every session and 1,594 once invoked, about $0.0004 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
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
chief-product-officer
Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market…
chief-technology-officer
Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…