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 javalenciacai/QASkills --skill user-story-verifiergit clone --depth 1 https://github.com/javalenciacai/QASkillsWrote 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/javalenciacai/qaskills/user-story-verifier)<a href="https://agentmods.dev/skills/javalenciacai/qaskills/user-story-verifier"><img src="https://agentmods.dev/badge/skills/javalenciacai/qaskills/user-story-verifier/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/javalenciacai/qaskills/user-story-verifier"><img src="https://agentmods.dev/badge/skills/javalenciacai/qaskills/user-story-verifier.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.00050 | $0.01989 |
| Opus 5 | $0.00025 | $0.00994 |
| Sonnet 5 | $0.00010 | $0.00398 |
| Haiku 4.5 | $0.00005 | $0.00199 |
Grade A, and why
user-story-static-verifier 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 11d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Story Static Verifier
This skill helps analyze user stories statically to verify their quality, completeness, and detect common defects.
When to Use
Use this skill when you need to review or validate user stories for:
- Completeness
- Clarity
- Adherence to agile principles
- INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable)
- Common requirement defects (ambiguity, omission, inconsistency, etc.)
How to Analyze a User Story
-
Check Format: Ensure it follows the standard format: "As a [role], I want [feature] so that [benefit]"
-
INVEST Criteria:
- Independent: The story should be self-contained and not depend on other stories.
- Negotiable: Details should be open to discussion with stakeholders.
- Valuable: The story must provide clear value to the end user.
- Estimable: The effort required should be estimable by the team.
- Small: The story should be small enough to complete within one sprint.
- Testable: There must be clear acceptance criteria to verify completion.
-
Additional Checks:
- Acceptance Criteria: Ensure they are specific, measurable, and testable.
- Clarity: Avoid ambiguous language; use clear, concise terms.
- Role Definition: The "As a" part should specify a real user role.
- Benefit: The "so that" part should explain the business value.
Requirement Defect Matrix
Scan user stories for these common defects:
1. Ambiguity
What it is: Use of subjective terms that can be interpreted differently by developers and QA.
Example ❌: "The system must load the report quickly."
Why it fails: What is "quickly"? 1s? 10s? Cannot be measured objectively.
Fix: "The system must load the report in under 3 seconds."
2. Omission
What it is: Missing critical information needed to develop or test the complete functionality.
Example ❌: "User can pay with credit card."
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.
- 11d ago First seen · 197 lines · 50 tokens per session scan A b1ae0f8294a9
user-story-static-verifier is a skill published in the GitHub repository javalenciacai/QASkills (5 stars, last pushed 7mo ago), licensed MIT. It adds 50 tokens to every session and 1,989 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-31.
Other skills, from other repositories
qa-expert
Expert-level quality assurance, testing strategies, automation, and QA processes. Use when the user mentions testing, test automation, quality assurance, or Selenium, or when the task involves Testing Types, QA Processes, Test Strategy, or Defect Management.
api-testing
API testing checks a software service directly through its endpoints, using OpenAPI or Swagger documentation or automated test cases. It can produce and run scripts that test requests and responses.
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
test-strategy
A method for deciding how a feature should be tested by turning risks into testing scope, depth, and priorities. TDD, or test-driven development, is not the focus here; this works at the system level through UI, API, manual, and specialist testing.
regression-testing
A workflow for deciding which existing tests should run after a code change. Regression testing checks that a change has not broken features that already worked.
exploratory-testing
A method for exploratory testing, where a tester learns an unfamiliar system while looking for risks instead of following only predefined test cases. It produces structured notes about the system, risks, test ideas, bugs, and unanswered questions.