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/rodrigorjsf/prd-generator-plugin/prd-newgit clone --depth 1 https://github.com/rodrigorjsf/prd-generator-pluginWrote 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/rodrigorjsf/prd-generator-plugin/prd-new)<a href="https://agentmods.dev/commands/rodrigorjsf/prd-generator-plugin/prd-new"><img src="https://agentmods.dev/badge/commands/rodrigorjsf/prd-generator-plugin/prd-new.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 | $0.00013 | $0.03430 |
| Opus 5 | $0.00006 | $0.01715 |
| Sonnet 5 | $0.00003 | $0.00686 |
| Haiku 4.5 | $0.00001 | $0.00343 |
Grade B, and why
prd-new scanned grade B with 1 finding 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 3d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
- $(ls .claude/skills/ | wc -l) project enforcement skills (including docs-stack + cicd) How it starts
The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/prd-new — PRD Generator
You orchestrate PRD generation: interrogation, research, architecture, documents, enforcement skills.
CRITICAL RULES:
- All generated files in English; respond to user in their language
- Each phase produces structured JSON for the next phase
- Dispatch research agents immediately when a technology/regulation is identified
- Never use forums, blogs, or social media as sources
PHASE 0 — Initialize
Create tasks to track progress:
- Interrogation
- Research & Validation
- Requirements Analysis
- Architecture Design
- Document Generation
- Skills & Guides Generation
- Commit
Initialize a context_packet object (held in memory throughout):
{
"meta": { "initiated_at": "<timestamp>", "language": "<user_language>" },
"identity": {},
"business": {},
"features": {},
"regulatory": {},
"integrations": {},
"infrastructure": {
"vcs": null,
"branch_strategy": null
},
"stack": {},
"repo_structure": "monorepo",
"research_refs": [],
"pending_research": []
}
Note: repo_structure is hardcoded as "monorepo" — this is a plugin-level rule, not a user choice. All projects generated by this plugin are monorepos.
If the user provided $1 (initial description), store it in context_packet.meta.initial_description and use it to pre-fill any obvious fields.
PHASE 1 — Product Interrogation (interactive)
Mark task "Interrogation" as in_progress.
Conduct the interrogation in blocks using a conversational, one-question-at-a-time format:
- Output each question as plain chat text (markdown) — do NOT use
AskUserQuestionfor interrogation blocks - Ask ONE question, then wait for the user's response before asking the next
- For questions with predefined options, present them as a numbered list:
[Question text]
1. Option A / 2. Option B / 3. Option C (Or type your own answer)
- After each block completes, check
pending_researchand dispatchofficial-researcheragents for any identified technology or regulated domain
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.
- 3d ago First seen · 340 lines · 13 tokens per session scan B 7b847d12e6ff
prd-new is a command published in the GitHub repository rodrigorjsf/prd-generator-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 3,430 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.