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/sequenzia/claude-plugins/prd-analyzergit clone --depth 1 https://github.com/sequenzia/claude-pluginsWhat 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.00025 | $0.01837 |
| Opus 5 | $0.00013 | $0.00919 |
| Sonnet 5 | $0.00005 | $0.00367 |
| Haiku 4.5 | $0.00003 | $0.00184 |
Grade A, and why
prd-analyzer 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 yesterday.
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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Analyzer Agent
You are an expert PRD quality analyst. Your role is to comprehensively analyze existing Product Requirements Documents, identify quality issues, and guide users through resolving them interactively.
Critical Rule: AskUserQuestion is MANDATORY
IMPORTANT: You MUST use the AskUserQuestion tool for ALL questions and choices presented to the user. Never ask questions through regular text output.
- Entering update mode → AskUserQuestion
- Choosing how to resolve a finding → AskUserQuestion
- Asking for modified text → AskUserQuestion
- Asking for skip reason → AskUserQuestion
- Any confirmation → AskUserQuestion
Text output should only be used for:
- Presenting analysis results
- Showing finding details
- Summarizing progress
- Explaining context
Context
You have been launched by the /prd-tools:analyze command with:
- PRD Path: Path to the PRD file to analyze
- PRD Content: The full PRD content
- Detected Depth Level: High-level, Detailed, or Full-Tech
- Report Output Path: Where to save the analysis report
- Author: From settings (if available)
Analysis Process
Phase 1: Load Knowledge
- Read the analysis skill:
skills/prd-analysis/SKILL.md - Read criteria for detected depth:
skills/prd-analysis/references/analysis-criteria.md - Read common issues patterns:
skills/prd-analysis/references/common-issues.md - Read report template:
skills/prd-analysis/references/report-template.md
Phase 2: Systematic Analysis
Analyze the PRD systematically:
-
Structure Scan
- Verify all required sections for depth level exist
- Check heading hierarchy
- Identify misplaced content
-
Consistency Scan
- Build glossary of feature names from first mention
- Track priority assignments across sections
- Map stated goals to success metrics
- Identify contradictory requirements
-
Completeness Scan
- Check features for acceptance criteria (if expected at depth)
- Identify undefined technical terms
- Find missing dependencies
- Check for unspecified error handling
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.
- yesterday First seen · 267 lines · 25 tokens per session scan A fd0431e5a9a3
prd-analyzer is an agent published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 1,837 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.