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/julianromli/droid-factory-template/create-prdgit clone --depth 1 https://github.com/julianromli/droid-factory-templateWrote 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/julianromli/droid-factory-template/create-prd)<a href="https://agentmods.dev/commands/julianromli/droid-factory-template/create-prd"><img src="https://agentmods.dev/badge/commands/julianromli/droid-factory-template/create-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.00006 | $0.01031 |
| Opus 5 | $0.00003 | $0.00515 |
| Sonnet 5 | $0.00001 | $0.00206 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
create-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 4d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule: Generating a Product Requirements Document (PRD)
Goal
To guide an AI assistant in creating a detailed Product Requirements Document (PRD) in Markdown format, based on an initial user prompt. The PRD should be clear, actionable, and suitable for a junior developer to understand and implement the feature.
Process
- Receive Initial Prompt: The user provides a brief description or request for a new feature or functionality.
- Ask Clarifying Questions: Before writing the PRD, the AI must ask only the most essential clarifying questions needed to write a clear PRD. Limit questions to 3-5 critical gaps in understanding. The goal is to understand the "what" and "why" of the feature, not necessarily the "how" (which the developer will figure out). Make sure to provide options in letter/number lists so I can respond easily with my selections.
- Generate PRD: Based on the initial prompt and the user's answers to the clarifying questions, generate a PRD using the structure outlined below.
- Save PRD: Save the generated document as
prd-[feature-name].mdinside the/tasksdirectory.
Clarifying Questions (Guidelines)
Ask only the most critical questions needed to write a clear PRD. Focus on areas where the initial prompt is ambiguous or missing essential context. Common areas that may need clarification:
- Problem/Goal: If unclear - "What problem does this feature solve for the user?"
- Core Functionality: If vague - "What are the key actions a user should be able to perform?"
- Scope/Boundaries: If broad - "Are there any specific things this feature should not do?"
- Success Criteria: If unstated - "How will we know when this feature is successfully implemented?"
Important: Only ask questions when the answer isn't reasonably inferable from the initial prompt. Prioritize questions that would significantly impact the PRD's clarity.
Formatting Requirements
- Number all questions (1, 2, 3, etc.)
- List options for each question as A, B, C, D, etc. for easy reference
- Make it simple for the user to respond with selections like "1A, 2C, 3B"
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.
- 4d ago First seen · 87 lines · 6 tokens per session scan A b189fe4704ef
create-prd is a command published in the GitHub repository julianromli/droid-factory-template (52 stars, last pushed 8mo ago), licensed MIT. It adds 6 tokens to every session and 1,031 once invoked, about $0.0000 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-30.
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.