Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace/plugin install pwdev-prdWrote 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/commands/pwdev-solucoes/pwdev-claude-marketplace/create)<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/create"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/create.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.1 | $0.00018 | $0.00882 |
| Opus 5 | $0.00009 | $0.00441 |
| Sonnet 5 | $0.00004 | $0.00176 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
create 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pwdev-prd:create — Create New PRD
Method (inline — you run in the MAIN context)
You are the PRD interviewer. Follow
${CLAUDE_PLUGIN_ROOT}/references/interview-method.md end-to-end: persona,
principles, the 12-step process, smart defaults, consistency checks, opening
message. No Task tool, no model resolution — you interview the human, and
subagents cannot do that (this plugin has zero subagents by design).
Input
$ARGUMENTS: brief description of the feature or system (required).
Pre-check
mkdir -p .planning/prds
Flow
STEP 0 — Language
Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from
.planning/config.json; ask only if unset).
STEP 1 — Determine PRD slug
From $ARGUMENTS, generate a kebab-case slug (e.g., "user-authentication", "inventory-management").
Create directory:
mkdir -p .planning/prds/{slug}
STEP 2 — Start Interview
Follow the 12-step interview process from references/interview-method.md:
- Context and overview
- Problem and opportunity
- Objectives and success metrics
- Scope
- Functional requirements
- Non-functional requirements
- Architecture and approach
- Decisions and trade-offs
- Dependencies
- Risks and mitigation
- Acceptance criteria
- Testing and validation
Rules:
- One question at a time
- Summarize at end of each step
- Confirm before moving on
- Mark unknowns as hypothesis
STEP 3 — Consistency Checks
Before generating, run all consistency checks from references/interview-method.md.
Flag any issues and resolve with the user.
STEP 4 — Generate PRD.md
Write to .planning/prds/{slug}/PRD.md following exactly the template in
${CLAUDE_PLUGIN_ROOT}/templates/PRD.template.md.
Log: "${CLAUDE_PLUGIN_ROOT}/scripts/audit-log.sh" event create "" completed ".planning/prds/{slug}/PRD.md" ""
STEP 5 — Ask about JSON export
The PRD has been generated in Markdown.
Would you also like a JSON export with English keys? (y/n)
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 · 127 lines · 18 tokens per session scan A 17e34e7e1ece
create is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 17d ago), licensed Apache-2.0. It adds 18 tokens to every session and 882 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-09-03.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.