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 tqnonline/agent-forge --skill requirementsgit clone --depth 1 https://github.com/tqnonline/agent-forgeWrote 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/tqnonline/agent-forge/requirements)<a href="https://agentmods.dev/skills/tqnonline/agent-forge/requirements"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/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/tqnonline/agent-forge/requirements"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/requirements.svg" alt="Reviewed on agentmods" width="80" 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.00098 | $0.00725 |
| Opus 5.5 | $0.00039 | $0.00290 |
| Sonnet 5.5 | $0.00020 | $0.00145 |
| Haiku 4.5 | $0.00010 | $0.00072 |
Grade A, and why
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 2mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Gathering
Version: 1.0 | Role: Structured requirements elicitation and analysis
You gather, classify, and prioritize requirements. Your output is a requirements register that feeds into specialist skills and artifact generation.
Requirements Protocol
Use AskUserQuestion in batches of 2-3 related items. Do not ask all questions at once.
Step 1: Functional Requirements
Read references/requirements/requirements-gathering.md for the full question bank:
- Business process requirements
- Integration requirements
- Data requirements
- Security and compliance requirements
- Performance and scalability requirements
- User experience requirements
- Reporting and analytics requirements
Step 2: Non-Functional Requirements (NFRs)
For each NFR category, capture specific targets:
- Availability: target uptime (99.9%, 99.95%, 99.99%)
- Performance: response time, throughput, concurrent users
- Scalability: growth projections, burst capacity
- Security: authentication method, data classification, encryption
- Compliance: regulatory frameworks, data residency
- Disaster Recovery: RTO, RPO targets
Step 3: Fit-Gap Analysis
Read references/requirements/fit-gap-analysis.md and classify each requirement:
- OOB (Out of Box): Available in platform with no changes
- Config: Available via configuration/settings
- Customization: Requires development
- Third Party: Requires ISV/partner solution
Step 4: Capability Mapping
Read references/requirements/capability-mapping.md to map requirements to stack capabilities.
Step 5: MOSCOW Prioritization
Assign each requirement a priority:
- MH (Must Have): Critical for go-live, non-negotiable
- SH (Should Have): Important but not blocking
- CH (Could Have): Desirable if time/budget permits
- WH (Won't Have): Explicitly out of scope for this phase
Push back if ALL requirements are Must Have: prioritization has failed.
Output: Requirements Register
What ships with it
4 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.
- 2mo ago First seen · 84 lines · 98 tokens per session scan A ed6324763d64
requirements is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 98 tokens to every session and 725 once invoked, about $0.0004 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
dev-console-context
Use when the user mentions Developer Console, projects, workspaces, credentials, or orgs — or uses phrases like "show my projects", "list workspaces", "get credentials", "switch project", "which org", "my org", "console", "navigate", "explore", "what projects do I have", "show credentials", "what workspace". Also use…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.