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/fmarzochi/egc/prp-prdgit clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/fmarzochi/egc/prp-prd)<a href="https://agentmods.dev/commands/fmarzochi/egc/prp-prd"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/prp-prd.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.00018 | $0.00923 |
| Opus 5 | $0.00009 | $0.00462 |
| Sonnet 5 | $0.00004 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
prp-prd 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Builder
Input: $ARGUMENTS
Build a Product Requirements Document by interviewing the user until the problem is understood, then writing the spec. The document is the output of the conversation, never a form filled in one shot.
Operating rule: the certainty board
Maintain a three-column board for the whole session:
| Column | Contents |
|---|---|
| Known | Facts the user stated or evidence you gathered |
| Assumed | Working hypotheses you adopted to move forward |
| Unknown | Questions that still block a trustworthy spec |
Every answer moves items between columns. You may only write the PRD when Unknown is empty or the user explicitly says "write it with what we have". Anything still in Assumed at writing time goes into the PRD's assumptions section, visible and testable.
Session flow
1. Seed
If $ARGUMENTS contains an idea, restate it in one sentence and place it in Assumed (it is a hypothesis, not a fact). If blank, open with exactly one question: "What problem keeps happening, and to whom?"
2. Question rounds
Ask in rounds of at most three questions. Never send a questionnaire. Pick the three questions that would eliminate the most Unknowns, favoring this order:
- Who has the problem and how do they cope today
- What evidence shows the problem is real (frequency, cost, complaints)
- What outcome would make the user say "solved"
- What must NOT change (constraints, integrations, budget)
- What happens if nothing is built
After each round, show the updated board in compact form so the user sees progress and can correct wrong Assumed entries.
3. Evidence pass
Before writing, verify what can be verified without the user:
- Search the repo for related code, prior attempts, TODO markers
- Check
PRPs/prds/for an earlier PRD on the same area - Note every verification in Known with its source
4. Write
Generate the document from the board. Kebab-case the title for the filename and save to:
PRPs/prds/{kebab-case-name}.prd.md
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 · 129 lines · 18 tokens per session scan A 81c8416edec5
prp-prd is a command published in the GitHub repository Fmarzochi/EGC (48 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 923 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
demand-discovery
Run automated niche demand discovery research across 7 data sources and 26 categories.
tdd-workflow
Implement the behavior described in $ARGUMENTS using strict TDD. Follow this exact sequence. Do not collapse phases. Each gate requires actual test runner output.
code-review
Review the code changes in this project. For each file changed.
refactor-file
Refactor the file specified in $ARGUMENTS following project conventions.
api-add-endpoint
Create a new API endpoint. $ARGUMENTS should describe the endpoint (e.g., "POST /api/users - create a user").
api-test-endpoint
Test the API endpoint specified in $ARGUMENTS.