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 HoangNguyen0403/agent-skills-standard --skill common-software-requirementsgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/common-software-requirements)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/common-software-requirements"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-software-requirements/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/hoangnguyen0403/agent-skills-standard/common-software-requirements"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-software-requirements.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.00053 | $0.00657 |
| Opus 5 | $0.00026 | $0.00329 |
| Sonnet 5 | $0.00011 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
common-software-requirements 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Requirements Expert
Priority: P0 (CRITICAL)
Define the technical "How" with verifiable requirements.
1. SRS/FRS Discovery
- Confirm linked PRD requirements (
REQ-*) and AC IDs. - Preserve trace:
BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> test evidence. - Block or route back to PRD (
plan-feature) whenREQ-*orAC-*inputs are missing; do not infer product scope from code. - Define functional flows: trigger, inputs, validations, outputs, errors.
- For complex flows, use one actor, one goal, one session; split normal, alternate, and exception courses.
- Define interface contracts: API, events, storage, external integrations.
- Define NFR thresholds: latency, availability, security, scalability.
- Define constraints: migration, compatibility, compliance, rollout.
2. Drafting Workflow
- Load
references/srs-template.md. - Slug Alignment: Use the same
[slug]from the sourcedocs/prd/prd-[slug].mdto maintain filename-level traceability. - Write one requirement card per statement with stable
SRS-*IDs. - Map each
SRS-*to source PRDREQ-*and verification lane. - Map every technical behavior to PRD ACs, test lane, and evidence target.
- Include statement, priority, status, input/output/error behavior, NFR impact, measurement method, and evidence target.
- Add outcome report:
feature_status, requirement trace, completed/missing evidence, decision needed, and recommended next workflow. - Write to
docs/srs/srs-[slug].md.
3. Verification Mapping
- Each
SRS-*has test evidence plan (unit/integration/E2E/manual). - Failure modes and fallback behavior are explicit.
- Permissions and privacy controls mapped to requirements.
- Measurement method exists for each NFR.
Anti-Patterns
- No mixed requirements and implementation tasks in same statement.
- No NFR claims without numeric threshold.
- No interface contract without input/output/error schema.
- No requirement without trace link to source and verification.
- No implementation handoff without mapped PRD AC IDs and test lanes.
- No happy-path-only flow for complex user/system interactions.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 68 lines · 53 tokens per session scan A ff3d6ec3a359
common-software-requirements is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 657 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-30.
Other skills, from other repositories
elite-engineer
The operating system for elite software engineering in TypeScript, React, and Next.js. Enforces the cognitive models, architecture laws, type-level patterns, component design, visual standards, and performance mandates that separate exceptional software from the ordinary — grounded in named sources (Torvalds…
oma-frontend
Frontend specialist for React, Next.js, Angular, TypeScript with FSD-lite architecture, shadcn/ui, and design system alignment. Use for UI, component, page, layout, CSS, Tailwind, shadcn, Angular, and RxJS work.
design-patterns
Frontend design patterns with React 19.2 and TypeScript 6 examples (Composition, Compound Components, Custom Hooks, Render Props, HOC, State Machines). Use when user asks "implement pattern", "use composition", or when designing reusable components.
react-nextjs
React 19.2 + Next.js 16 development - Server Components, Cache Components, proxy.ts, View Transitions, App Router, TypeScript 6, and Tailwind CSS v4. Use when building frontend apps, creating components, or asking "how do I set up X?".
code-quality
Comprehensive frontend code review for TypeScript 6 and React 19.2 — clean code principles, component patterns, type safety, accessibility, and performance. Use when user says "review code", "refactor", "check this PR", or before merging changes.
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.