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/ddunnock/claude-plugins/requirements-devnpx skills add ddunnock/claude-plugins --skill requirements-devgit clone --depth 1 https://github.com/ddunnock/claude-pluginsWhat 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 | $0.00103 | $0.03825 |
| Opus 5 | $0.00051 | $0.01912 |
| Sonnet 5 | $0.00021 | $0.00765 |
| Haiku 4.5 | $0.00010 | $0.00382 |
Grade A, and why
requirements-dev 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 2d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Development (INCOSE GtWR v4)
Transform concept development artifacts into formal, INCOSE-compliant requirements through a structured three-phase pipeline with gate-controlled progression.
Deliverables
This skill produces three primary documents plus supporting registries:
| Deliverable | Format | Content |
|---|---|---|
| REQUIREMENTS-SPECIFICATION.md | Markdown | All requirements organized by block and type |
| TRACEABILITY-MATRIX.md | Markdown | Bidirectional chain: source → need → requirement → V&V |
| VERIFICATION-MATRIX.md | Markdown | All requirements with V&V methods, criteria, status |
| *.reqif | XML | Optional ReqIF interchange export |
| JSON registries | JSON | needs, requirements, traceability, sources, assumptions, notes |
What ships with it
60 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.
- .claude-plugin/plugin.json 1.2 KB
- agents/document-writer.md 2.6 KB
- agents/gap-analyst.md 8.8 KB
- agents/quality-checker.md 4.7 KB
- agents/skeptic.md 2.0 KB
- agents/tpm-researcher.md 5.6 KB
- commands/reqdev.decompose.md 5.3 KB
- commands/reqdev.deliver.md 5.5 KB
- commands/reqdev.gaps.md 8.3 KB
- commands/reqdev.init.md 11 KB
- commands/reqdev.needs.md 8.9 KB
- commands/reqdev.requirements.md 17 KB
- commands/reqdev.research.md 4.3 KB
- commands/reqdev.resume.md 6.6 KB
- commands/reqdev.status.md 5.0 KB
- commands/reqdev.validate.md 7.5 KB
- CROSS-SKILL-ANALYSIS.md 17 KB
- data/absolutes.json 50 B
- data/escape_clauses.json 211 B
- data/pronouns.json 73 B
- data/vague_terms.json 242 B
- hooks/hooks.json 426 B
- hooks/scripts/update-state-on-write.sh 2.4 KB runs code
- HOW_TO_USE.md 22 KB
- pyproject.toml 199 B
- README.md 19 KB
- references/attribute-schema.md 2.2 KB
- references/decomposition-guide.md 2.4 KB
- references/incose-rules.md 6.0 KB
- references/type-guide.md 3.3 KB
- references/vv-methods.md 2.4 KB
- scripts/assumption_tracker.py 11 KB runs code
- scripts/check_tools.py 5.6 KB runs code
- scripts/decompose.py 7.8 KB runs code
- scripts/gap_analyzer.py 19 KB runs code
- scripts/ingest_concept.py 6.3 KB runs code
- scripts/init_session.py 2.8 KB runs code
- scripts/needs_tracker.py 13 KB runs code
- scripts/notes_tracker.py 13 KB runs code
- scripts/quality_rules.py 15 KB runs code
- scripts/reqif_export.py 11 KB runs code
- scripts/requirement_tracker.py 15 KB runs code
- scripts/set_validator.py 13 KB runs code
- scripts/shared_io.py 1.9 KB runs code
- scripts/source_tracker.py 4.1 KB runs code
- scripts/traceability.py 8.2 KB runs code
- scripts/update_state.py 8.8 KB runs code
- templates/requirements-specification.md 1.8 KB
- templates/state.json 927 B
- templates/traceability-matrix.md 1.3 KB
- templates/verification-matrix.md 1.8 KB
- tests/__init__.py 0 B runs code
- tests/conftest.py 1.6 KB runs code
- tests/test_assumption_tracker.py 10 KB runs code
- tests/test_decomposition.py 9.9 KB runs code
- tests/test_gap_analyzer.py 17 KB runs code
- tests/test_ingest_concept.py 10 KB runs code
- tests/test_init_session.py 2.6 KB runs code
- tests/test_integration.py 21 KB runs code
- tests/test_needs_tracker.py 11 KB runs code
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.
- 2d ago First seen · 247 lines · 103 tokens per session scan A 69a93e00517b
requirements-dev is a skill published in the GitHub repository ddunnock/claude-plugins (12 stars, last pushed 5mo ago), licensed MIT. It adds 103 tokens to every session and 3,825 once invoked, about $0.0005 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
bmad-check-implementation-readiness
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".