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/saolalab/clawforce/requirements-analysisnpx skills add saolalab/clawforce --skill requirements-analysisgit clone --depth 1 https://github.com/saolalab/clawforceWrote 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/saolalab/clawforce/requirements-analysis)<a href="https://agentmods.dev/skills/saolalab/clawforce/requirements-analysis"><img src="https://agentmods.dev/badge/skills/saolalab/clawforce/requirements-analysis.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 | $0.00019 | $0.00349 |
| Opus 5 | $0.00010 | $0.00175 |
| Sonnet 5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
requirements-analysis 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 4d 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.
What it actually says
Requirements Analysis
Requirements Types
| Type | Description | Example |
|---|---|---|
| Business | What the business needs | "Reduce processing time by 50%" |
| Functional | What the system does | "System shall calculate tax" |
| Non-functional | How the system performs | "Page loads in <2 seconds" |
| Constraints | Limitations | "Must use existing database" |
Elicitation Techniques
- Interviews: One-on-one with stakeholders
- Workshops: Group sessions
- Observation: Watch users work
- Document Analysis: Review existing docs
- Prototyping: Show and iterate
User Story Format
As a [role]
I want [feature]
So that [benefit]
Acceptance Criteria:
- Given [context]
- When [action]
- Then [outcome]
Requirements Documentation
Business Requirements Document (BRD)
- Executive summary
- Business objectives
- Scope and constraints
- Stakeholders
- Requirements list
- Success metrics
Traceability Matrix
| Req ID | Description | Source | Priority | Status |
|---|---|---|---|---|
| REQ-001 | ... | Stakeholder A | High | Approved |
Validation Checklist
- Stakeholders have reviewed
- Requirements are testable
- No conflicts between requirements
- Priorities are assigned
- Dependencies identified
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.
- 4d ago First seen · 62 lines · 19 tokens per session scan A 2f6ed8f89034
requirements-analysis is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 349 once invoked, about $0.0001 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
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
add-matrix
Add Matrix channel integration via Chat SDK. Works with any Matrix homeserver.
add-resend
Add Resend (email) channel integration via Chat SDK.
add-macos-statusbar
Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.