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/kamiazya/scopes/prd-parsegit clone --depth 1 https://github.com/kamiazya/scopesWhat 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.00000 | $0.01339 |
| Opus 5 | $0.00000 | $0.00669 |
| Sonnet 5 | $0.00000 | $0.00268 |
| Haiku 4.5 | $0.00000 | $0.00134 |
Grade A, and why
prd-parse 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Parse
Convert PRD to technical implementation epic.
Usage
/pm:prd-parse <feature_name>
Required Rules
IMPORTANT: Before executing this command, read and follow:
.claude/rules/datetime.md- For getting real current date/time
Preflight Checklist
Before proceeding, complete these validation steps. Do not bother the user with preflight checks progress ("I'm not going to ..."). Just do them and move on.
Validation Steps
-
Verify <feature_name> was provided as a parameter:
- If not, tell user: "❌ <feature_name> was not provided as parameter. Please run: /pm:prd-parse <feature_name>"
- Stop execution if <feature_name> was not provided
-
Verify PRD exists:
- Check if
.claude/prds/$ARGUMENTS.mdexists - If not found, tell user: "❌ PRD not found: $ARGUMENTS. First create it with: /pm:prd-new $ARGUMENTS"
- Stop execution if PRD doesn't exist
- Check if
-
Validate PRD frontmatter:
- Verify PRD has valid frontmatter with: name, description, status, created
- If frontmatter is invalid or missing, tell user: "❌ Invalid PRD frontmatter. Please check: .claude/prds/$ARGUMENTS.md"
- Show what's missing or invalid
-
Check for existing epic:
- Check if
.claude/epics/$ARGUMENTS/epic.mdalready exists - If it exists, ask user: "⚠️ Epic '$ARGUMENTS' already exists. Overwrite? (yes/no)"
- Only proceed with explicit 'yes' confirmation
- If user says no, suggest: "View existing epic with: /pm:epic-show $ARGUMENTS"
- Check if
-
Verify directory permissions:
- Ensure
.claude/epics/directory exists or can be created - If cannot create, tell user: "❌ Cannot create epic directory. Please check permissions."
- Ensure
Instructions
You are a technical lead converting a Product Requirements Document into a detailed implementation epic for: $ARGUMENTS
1. Read the PRD
- Load the PRD from
.claude/prds/$ARGUMENTS.md - Analyze all requirements and constraints
- Understand the user stories and success criteria
- Extract the PRD description from frontmatter
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 · 176 lines · 0 tokens per session scan A 2aa344eafaf8
prd-parse is a command published in the GitHub repository kamiazya/scopes (2 stars, last pushed 9mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,339 tokens. 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
review.v1
Review code changes: /review [commit|branch|PR].
diagnose-deeptrace
Run a ZDX deep trace diagnostics session — start, analyze, or clean up deep traces for a user's device.
troubleshoot-user
Cross-product troubleshooting of user connectivity across ZCC, ZDX, ZPA, and ZIA.
audit-ssl
Audit ZIA SSL inspection rules -- list rules by action (INSPECT, DONOTINSPECT, DONOTDECRYPT, BLOCK), identify bypasses, and assess risk.
investigate-incident
Investigate security incidents using Z-Insights analytics -- threats, firewall actions, shadow IT, and web traffic.
create-access-rule
Create a ZPA access policy rule with v2 conditions for application access control.