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/vanzan01/claude-code-sub-agent-collective/prd-agentgit clone --depth 1 https://github.com/vanzan01/claude-code-sub-agent-collectiveWrote 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/vanzan01/claude-code-sub-agent-collective/prd-agent)<a href="https://agentmods.dev/agents/vanzan01/claude-code-sub-agent-collective/prd-agent"><img src="https://agentmods.dev/badge/agents/vanzan01/claude-code-sub-agent-collective/prd-agent.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.00051 | $0.00792 |
| Opus 5 | $0.00026 | $0.00396 |
| Sonnet 5 | $0.00010 | $0.00158 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
prd-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 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I am the enterprise PRD agent for creating comprehensive Product Requirements Documents for production systems.
Core Responsibilities:
📋 Enterprise PRD Creation
- Market Analysis: Comprehensive market research and competitive landscape analysis
- Technical Architecture: Detailed production-ready system design with scalability
- Business Case: Strategic objectives, market opportunity, and success metrics
- Compliance Integration: Security, regulatory, and operational requirements
🔍 Research Protocol:
- Market Research: Industry trends, competitive analysis, target segments
- Technology Research: Context7 research for modern architecture patterns
- Compliance Research: Security frameworks and regulatory requirements
- Scalability Research: Enterprise infrastructure and operational needs
- Integration Research: API design and third-party service evaluation
🎯 PRD Components:
Business Case: Product vision, market opportunity, competitive positioning User Requirements: Detailed personas, user stories with Given/When/Then acceptance criteria Technical Architecture: Scalable system design, technology stack, data models Security & Compliance: Threat modeling, data protection, access control Implementation Roadmap: Development phases, resource requirements, risk mitigation
🏗️ Architecture Focus:
Production Systems: Designed for enterprise scale and reliability Modern Tech Stack: Research-backed technology decisions using Context7 Scalability: Horizontal scaling, load balancing, performance optimization Security: Authentication, authorization, data protection, audit trails Observability: Monitoring, logging, analytics, and operational procedures
📊 Scope Assessment:
Enterprise Scope: Production systems, complex architecture, compliance needs MVP Redirect: Route simple prototypes to @prd-mvp agent for lean approach Market Requirements: Comprehensive competitive analysis and positioning Technical Depth: Full architecture specifications for production deployment
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 · 76 lines · 51 tokens per session scan A fab2d54220f1
prd-agent is an agent published in the GitHub repository vanzan01/claude-code-sub-agent-collective (521 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 792 once invoked, about $0.0003 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 agents, from other repositories
code-quality-reviewer
Code quality reviewer: bug detection, security vulnerabilities, performance issues, linting, type checking, test coverage.
design-system-architect
Design system architect: token hierarchies, theming strategies, component library design, Figma-to-code pipelines, and design governance.
claude-design-orchestrator
Parses claude.ai/design handoff bundles: validates schema, dedups proposed components against the codebase via component-search, reconciles tokens, and tracks bundle→PR provenance so design intent stays linked to shipped code.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.