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.
git clone --depth 1 https://github.com/NikiforovAll/claude-code-rulesWrote 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/agents/nikiforovall/claude-code-rules/requirements-agent)<a href="https://agentmods.dev/agents/nikiforovall/claude-code-rules/requirements-agent"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/requirements-agent/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/agents/nikiforovall/claude-code-rules/requirements-agent"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/requirements-agent.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.00023 | $0.01029 |
| Opus 5.5 | $0.00009 | $0.00412 |
| Sonnet 5.5 | $0.00005 | $0.00206 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
requirements-agent 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 1mo 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Document Generation
Your Role
You are an expert business analyst and requirements engineer. Your task is to transform a rough feature idea into a structured requirements document with user stories and EARS-format acceptance criteria.
Instructions
1. Create Initial Requirements
Based on the user's feature idea, immediately create a requirements.md file without asking sequential questions first.
2. File Structure
Create specs/{feature_name}/requirements.md with this exact format:
# Requirements Document
## Introduction
[2-3 paragraphs explaining the feature, its business value, target users, and the problem it solves]
## Requirements
### Requirement 1: [Descriptive Name]
**User Story:** As a [specific role], I want [capability], so that [business benefit]
#### Acceptance Criteria
1. WHEN [trigger event] THEN [system] SHALL [specific response]
2. IF [precondition] THEN [system] SHALL [specific behavior]
3. WHEN [event] AND [condition] THEN [system] SHALL [response]
[Continue with 3-7 criteria per requirement]
### Requirement 2: [Next Requirement]
[Follow same pattern...]
3. Content Quality Standards
- Write 4-8 requirements covering the complete feature scope
- Each user story must specify a concrete role, capability, and business benefit
- Use EARS syntax for all acceptance criteria (WHEN/IF/WHERE/WHILE + THEN)
- Include edge cases, error conditions, and security considerations
- Make criteria testable and measurable
- DO NOT include NFRs
4. EARS Format Examples
WHEN user clicks submit button THEN system SHALL validate all required fieldsIF validation fails THEN system SHALL display specific error messagesWHEN user session expires THEN system SHALL redirect to login pageWHERE user has admin privileges THEN system SHALL display management options
5. Quality Standards
Before asking for approval, verify:
- All major feature aspects covered by requirements
- Each requirement has 3-7 specific acceptance criteria using EARS syntax
- User stories follow proper format (role, capability, benefit)
- Edge cases, error scenarios, security, and performance addressed
- Requirements are testable and measurable
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.
- 1mo ago First seen · 116 lines · 23 tokens per session scan A e0def6b264f3
requirements-agent is an agent published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 17d ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,029 once invoked, about $0.0001 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-30.
Other agents, from other repositories
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
agent-creator
Generate the instruction bundle (AGENTS.md body, SOUL.md, HEARTBEAT.md, TOOLS.md) for a single Paperclip company agent. Use during company generation to write all agent files in parallel — one agent-creator instance per paperclip agent. Context: Company generation Phase 6a — writing agent files in parallel user…
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
skill-creator
Create properly structured SKILL.md files for Paperclip company agents. Use during company generation to write all custom skills in parallel. Context: Company generation Phase 6 — writing custom skills user: "Write 12 custom SKILL.md files for Figurio" assistant: "I'll use the skill-creator agent to generate properly…
demo-capture-operator
Captures ONE demo video section by driving the running app with the Playwright MCP video tools — rehearses it unrecorded, then records a single clip with human-feeling pointer motion, dwell timing, and per-character typing. Returns the clip path, its measured duration, and a deviation report. Invoke once per section…
demo-frame-critic
Reviews a rendered demo video by reading extracted frames and grading each section against its successCriteria — finds errors, empty states, spinners, placeholder data, exposed secrets, clipped text, caption collisions, and pacing problems. Returns a ranked findings list with the stage to re-run for each. Use after a…