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 nasrulhazim/claude --skill project-requirementsgit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/nasrulhazim/claude/project-requirements)<a href="https://agentmods.dev/skills/nasrulhazim/claude/project-requirements"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/project-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/nasrulhazim/claude/project-requirements"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/project-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.00168 | $0.02960 |
| Opus 5 | $0.00084 | $0.01480 |
| Sonnet 5 | $0.00034 | $0.00592 |
| Haiku 4.5 | $0.00017 | $0.00296 |
Grade A, and why
project-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 10d 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Requirements
Interview-driven requirements engineering — from stakeholder discovery through traceable specifications. Produces IEEE 830-inspired SRS documents, user stories with acceptance criteria, client-facing proposals, ASCII wireframes, and full traceability matrices.
How It Works
- Interview first — every command starts by gathering context through structured questions
- Generate artefact — produce the document using reference templates
- Cross-link — connect requirements to stories, stories to tests, tests back to requirements
Always check if an existing SRS or requirements document exists before starting from scratch. If the user pastes requirements inline, extract and structure them rather than re-asking.
Command Reference
| Command | Description |
|---|---|
/req spec |
Interview → generate SRS document (IEEE 830 simplified) |
/req stories |
Generate user stories with acceptance criteria from SRS or interview |
/req proposal |
Client-facing project proposal with scope, timeline, pricing |
/req wireframe |
ASCII wireframe generation for key screens |
/req matrix |
Traceability matrix (requirement → story → test) |
1. /req spec — Software Requirements Specification
Interview Phase
Ask questions in four blocks, one at a time:
Block 1 — Project Identity
- What is the project/system name?
- What problem does it solve? (one sentence)
- Who is the primary user? Who are secondary users?
- What is the business context? (internal tool, client project, product, government system)
Block 2 — Functional Requirements
- What are the 5–10 core features the system must have?
- For each feature: what does the user do, and what does the system respond with?
- Are there any workflows that span multiple features? Describe them.
- What data does the system manage? (entities, relationships at a high level)
Block 3 — Non-Functional Requirements
- Performance expectations? (response time, concurrent users, data volume)
- Security requirements? (authentication, authorisation, data protection, PDPA compliance)
- Availability and uptime requirements?
- Technology constraints? (hosting, framework, language, integrations)
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.
- 10d ago First seen · 326 lines · 168 tokens per session scan A beb67ed658a9
project-requirements is a skill published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 8d ago), licensed MIT. It adds 168 tokens to every session and 2,960 once invoked, about $0.0008 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
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…