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 skills add sequenzia/claude-plugins --skill prd-analysisgit clone --depth 1 https://github.com/sequenzia/claude-pluginsWrote 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/sequenzia/claude-plugins/prd-analysis)<a href="https://agentmods.dev/skills/sequenzia/claude-plugins/prd-analysis"><img src="https://agentmods.dev/badge/skills/sequenzia/claude-plugins/prd-analysis/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/skills/sequenzia/claude-plugins/prd-analysis"><img src="https://agentmods.dev/badge/skills/sequenzia/claude-plugins/prd-analysis.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.00019 | $0.01557 |
| Opus 5.5 | $0.00008 | $0.00623 |
| Sonnet 5.5 | $0.00004 | $0.00311 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade A, and why
prd-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 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Analysis Skill
This skill provides structured knowledge for analyzing existing Product Requirements Documents to identify quality issues and guide resolution.
Analysis Philosophy
Depth-Aware Analysis
PRD analysis must respect the intended depth level of the document. A high-level PRD should not be flagged for missing API specifications, just as a full-tech PRD should be scrutinized for technical completeness.
Key Principle: Only flag what's expected at the document's depth level.
Constructive Approach
Findings should be:
- Actionable: Clear recommendation for how to fix
- Specific: Exact location and description of issue
- Prioritized: Severity indicates importance
- Helpful: Explain why this matters, not just what's wrong
Systematic Coverage
Analysis covers four distinct categories to ensure comprehensive review:
- Inconsistencies: Internal contradictions or mismatches
- Missing Information: Expected content that's absent
- Ambiguities: Unclear or vague statements
- Structure Issues: Formatting, organization, missing sections
Finding Categories
1. Inconsistencies
Issues where the PRD contradicts itself or uses conflicting information.
What to Look For:
- Feature named differently in different sections
- Priority mismatches (feature marked P2 but in Phase 1)
- Metrics that don't align with stated goals
- Contradictory requirements
- Timeline/phase misalignment
Detection Strategy:
- Build glossary of feature names from first mention
- Track priority assignments
- Map goals to metrics
- Compare requirements for conflicts
2. Missing Information
Expected content that is absent based on the PRD's depth level.
What to Look For:
- Required sections for depth level
- Undefined technical terms
- Features without acceptance criteria (detailed/full-tech)
- Error scenarios not addressed
- Dependencies not listed
- Incomplete personas
Detection Strategy:
- Compare against depth-level checklist
- Identify domain terms without definitions
- Check each feature for expected attributes
- Scan for external system references
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 269 lines · 19 tokens per session scan A 8f3c571a4151
prd-analysis is a skill published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 19 tokens to every session and 1,557 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…