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 commands/sequenzia/claude-plugins/analyzegit 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.00018 | $0.00856 |
| Opus 5 | $0.00009 | $0.00428 |
| Sonnet 5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00086 |
Grade A, and why
analyze 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Analyzer - Analyze Command
You are initiating the PRD analysis workflow. This process will analyze an existing PRD for quality issues and optionally guide the user through resolving them interactively.
Workflow
Step 1: Validate File
Verify the PRD file exists at the provided path. If not found:
- Check if user provided relative path and try common locations
- Use Glob to search for similar filenames
- Ask user for correct path if needed
Step 2: Read PRD Content
Read the entire PRD file using the Read tool.
Step 3: Detect Depth Level
Analyze the PRD content to detect its depth level:
Full-Tech Indicators (check first):
- Contains
API Specificationssection OR### 7.4 APIor similar - Contains API endpoint definitions (
POST /api/,GET /api/, etc.) - Contains
Testing Strategysection - Contains data model schemas
Detailed Indicators:
- Uses numbered sections (
## 1.,### 2.1) - Contains
Technical Architecturesection - Contains user stories (
**US-001**:or similar format) - Contains acceptance criteria
High-Level Indicators:
- Contains feature table with Priority column
- Executive summary focus
- No user stories or acceptance criteria
- Shorter document (~50-100 lines)
Detection Priority:
- If Full-Tech indicators found → Full-Tech
- Else if Detailed indicators found → Detailed
- Else if High-Level indicators found → High-Level
- Default → Detailed
Step 4: Check Settings
Check for settings at .claude/prd-tools.local.md to get:
- Author name (if configured)
- Any custom preferences
Step 5: Determine Report Path
The analysis report should be saved in the same directory as the PRD with .analysis.md suffix:
- PRD:
specs/PRD-User-Auth.md - Report:
specs/PRD-User-Auth.analysis.md
Extract the PRD filename and construct the report path.
Step 6: Launch Analyzer Agent
Launch the PRD Analyzer Agent using the Task tool with subagent_type prd-tools:prd-analyzer.
Provide this context in the prompt:
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 · 128 lines · 18 tokens per session scan A 863491d72fc5
analyze is a command published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 856 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.