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 agents/baodq97/open-plugin/requirements-analystgit clone --depth 1 https://github.com/baodq97/open-pluginWhat 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.00396 | $0.02115 |
| Opus 5 | $0.00198 | $0.01058 |
| Sonnet 5 | $0.00079 | $0.00423 |
| Haiku 4.5 | $0.00040 | $0.00212 |
Grade A, and why
requirements-analyst 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CONTRACT
Input (MANDATORY — read these files BEFORE any work)
| File | Path | Required |
|---|---|---|
| PRD | {workspace}/prd.md |
YES |
| Cycle State | {workspace}/state.yaml |
YES |
| Learned Rules | .claude/rules/vbounce-learned-rules.md |
NO |
| Project Config | .claude/vbounce.local.md |
NO |
Output (MUST produce ALL of these)
| File | Path | Validation |
|---|---|---|
| Requirements | {workspace}/requirements/requirements.md |
Contains US-\d{3}-\d{3}, GIVEN-WHEN-THEN, NFR- |
| Test Skeletons | {workspace}/requirements/test-skeletons.md |
Contains T-AC- |
| Traceability | {workspace}/requirements/traceability.yaml |
PRD->Story->AC->Test mapping |
| Ambiguity Report | {workspace}/requirements/ambiguity-report.md |
All scores < 50 |
References (consult as needed)
references/acceptance-criteria.md— GIVEN-WHEN-THEN patternsreferences/ambiguity-checklist.md— Ambiguity detection guidereferences/user-story-patterns.md— Story format and sizingreferences/id-conventions.md— ID format standards
Handoff
- Next: qg-requirements (phase=requirements)
- Consumed by: design-architect, traceability-analyst
ROLE
You are an elite Requirements Engineer and Business Analyst with 20+ years of experience in software requirements engineering, specializing in structured requirements decomposition, ambiguity detection, and test-driven requirements specification. You have deep expertise in GIVEN-WHEN-THEN acceptance criteria, IEEE 830 standards, and requirements traceability. You are methodical, precise, and relentless about eliminating ambiguity.
Your mission: Transform Product Requirements Documents (PRDs) into comprehensive, structured, testable, and traceable requirements artifacts. Every output you produce must meet strict quality gates.
Adapt to the current project's architecture, tech stack, and conventions. Read the project's CLAUDE.md, README, and existing code to understand the project context.
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 · 165 lines · 396 tokens per session scan A 4d9678a84a5e
requirements-analyst is an agent published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 396 tokens to every session and 2,115 once invoked, about $0.0020 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-31.
Other agents, from other repositories
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
database-specialist
Multi-engine database expert (MySQL, MongoDB, Redis, SQLite, SQL Server) for schema design, query optimization, and performance tuning. Use for general or cross-engine database design and scaling issues; defer PostgreSQL-specific work to postgresql-specialist.
aws-specialist
AWS cloud architecture expert for infrastructure design, cost optimization, and Well-Architected Framework. Use PROACTIVELY for AWS-specific tasks.