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/pan94u/forge/requirement-engineeringnpx skills add pan94u/forge --skill requirement-engineeringgit clone --depth 1 https://github.com/pan94u/forgeWhat 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.00032 | $0.01488 |
| Opus 5 | $0.00016 | $0.00744 |
| Sonnet 5 | $0.00006 | $0.00298 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
requirement-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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 183 lines · 32 tokens per session scan A e785cbec2247
requirement-engineering is a skill published in the GitHub repository pan94u/forge (40 stars, last pushed 1mo ago), with no licence file. It adds 32 tokens to every session and 1,488 once invoked, about $0.0002 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
tsq-grill
소크라틱 심층 인터뷰로 PRD와 Sub-PRD를 작성/보강하는 스킬. 3모드 자동 분기: PRD 미존재 시 프로젝트 전체 인터뷰, PRD 존재 시 기능별 심층 인터뷰, PRD가 있지만 빈 섹션이 있으면 보강 인터뷰. 프로젝트 시작, 아이디어 구체화, 요구사항 정리가 필요한 모든 순간에 사용한다. Use when: "PRD 작성", "기획", "기능 상세화", "요구사항 인터뷰", "PRD 보강", "grill", "기능 정의", "Sub-PRD 작성", "기능 스펙 잡기", "프로젝트 정의", "뭘 만들지 정리", "아이디어 구체화", "스코프 잡기", "기획서"…
tsq-planning
기획 및 요건 정의 가이드라인. PRD, 요구사항 정의, 문서 구조화, 대용량 문서 분할 전략을 다룸. Use when: "기획, PRD, 요구사항, 요건 정의, 스코프, 마일스톤".
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
requirement-study
Analyze, write, and validate software requirements from any input — conversations, documents, rough notes, or existing specs. Use when someone asks to study requirements, create a PRD, analyze a feature request, extract requirements from a document, or validate completeness of existing requirements. Also triggers on…
openspec-update-change
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
verify-openspec-docs
Fact-checks OpenSpec user documentation with a fresh-context subagent that re-runs commands and checks claims against source. Manually triggered; not part of the drafting loop. Use when the user asks to verify, fact-check, or accuracy-check a docs page, section, or set of changed claims.