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 agentmods add skills/zeeshanhanif/agentic-sdlc-kit/requirements-engineeringnpx skills add zeeshanhanif/agentic-sdlc-kit --skill requirements-engineeringgit clone --depth 1 https://github.com/zeeshanhanif/agentic-sdlc-kitWrote 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/zeeshanhanif/agentic-sdlc-kit/requirements-engineering)<a href="https://agentmods.dev/skills/zeeshanhanif/agentic-sdlc-kit/requirements-engineering"><img src="https://agentmods.dev/badge/skills/zeeshanhanif/agentic-sdlc-kit/requirements-engineering.svg" alt="Measured on agentmods" 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.00212 | $0.02887 |
| Opus 5 | $0.00106 | $0.01443 |
| Sonnet 5 | $0.00042 | $0.00577 |
| Haiku 4.5 | $0.00021 | $0.00289 |
Grade A, and why
requirements-engineering 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 5d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Engineering
This skill produces the traditional, structured requirements specification that sits at the very front of the SDLC — upstream of architecture and UX. It is deliberately a detail phase: its job is to capture every requirement comprehensively, so that the documents it produces become the single source of truth the design and planning skills downstream consume.
Two principles define it:
-
Exhaustive enumeration, not transcription. When a capability area comes up, the skill does not merely record what the user mentions. It proactively proposes the full set of standard sub-requirements for that area and has the user confirm, extend, or remove them. "User authentication" is never one line — it expands into sign-up, sign-in, email verification, forgot password, reset password, change password, logout, session expiry, account lockout, rate limiting, and so on. The
requirement-catalog.mdreference is the engine for this. The same discipline applies to non-functional requirements. -
Structured and traditional. The output is a formal SRS in the ISO/IEC/IEEE 29148 (IEEE 830) lineage — numbered, uniquely-identified, testable requirements — not an agile backlog. Whatever the SRS calls a unit (function / feature) is fine; epic and feature slicing is deliberately deferred to the downstream implementation-planning skill. This skill owns the problem space, comprehensively.
Because a full requirements interview is long, the skill checkpoints its work
incrementally and can resume after an interruption — see Phase 0 and
references/checkpointing.md.
Inputs
This is the first skill in the pipeline, so it has no upstream document to consume — it elicits from the user. If the user has an existing brief, notes, or partial requirements, ingest them first and treat them as raw input to confirm and expand, not as finished requirements.
Outputs
Three files (three logical documents), all markdown, written to docs/.
What ships with it
8 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.
- 5d ago First seen · 237 lines · 212 tokens per session scan A 05de7795f5c0
requirements-engineering is a skill published in the GitHub repository zeeshanhanif/agentic-sdlc-kit (5 stars, last pushed 9d ago), licensed Apache-2.0. It adds 212 tokens to every session and 2,887 once invoked, about $0.0011 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…