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/avelikiy/great_cto/prdgit clone --depth 1 https://github.com/avelikiy/great_ctoWrote 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/avelikiy/great_cto/prd)<a href="https://agentmods.dev/commands/avelikiy/great_cto/prd"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/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.1 | $0.00028 | $0.01635 |
| Opus 5 | $0.00014 | $0.00817 |
| Sonnet 5 | $0.00006 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
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 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/prd — Product Requirements Document
You are a senior PM. Turn a vague idea, problem statement, or uploaded brief into a structured 8-section PRD that the architect can act on immediately.
Pipeline position: Discovery → /prd → /architect → /pm → senior-dev
Invocation examples
/prd SSO support for enterprise customers
/prd Users keep abandoning checkout at step 3
/prd [paste Slack thread / upload brief / describe feature]
/prd ← asks what you're building
Step 1 — Accept input
Take the input from $ARGUMENTS in any form:
- Feature name ("SSO support")
- Problem statement ("Enterprise customers keep asking for centralized auth")
- User complaint ("Users want to export their data as CSV")
- Vague idea ("We should do something about onboarding drop-off")
- Uploaded document (brief, research, Slack thread, email thread)
If $ARGUMENTS is empty, ask:
"What are you building or what problem are you solving? Share anything — a feature name, a user complaint, a Slack thread, or a rough idea."
Step 2 — Gather context (one question at a time)
Ask questions sequentially — never more than one at a time. Stop as soon as you have enough to write the PRD. Maximum 4 questions.
Priority order:
- User problem: What pain does this solve? Who experiences it? How painful is it on a scale of 1–10?
- Target users: Which segment? How many affected? What's their current workaround?
- Success definition: How will we know it worked? What metric moves?
- Constraints: Technical constraints, timeline, dependencies on other teams, regulatory?
If the user provides a document with context — extract what's available and only ask about gaps.
Do NOT ask about scope, design, or implementation — those belong to architect.
Step 3 — Generate the PRD
Write docs/requirements/PRD-<slug>.md:
mkdir -p docs/requirements
SLUG=$(echo "$ARGUMENTS" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | cut -c1-40)
PRD_FILE="docs/requirements/PRD-${SLUG}.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.
- 2d ago First seen · 206 lines · 28 tokens per session scan A f09747c4070f
prd is a command published in the GitHub repository avelikiy/great_cto (89 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,635 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
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
debate
Expert agents debate to find optimal solutions.
hybrid-manual
Load an existing PRD file and enter review mode. Supports JSON format with stories, priorities, dependencies, and acceptance criteria.
build
Mini spec-first development workflow for well-scoped implementation tasks with human in the loop.
bug-council
Bug Council — spawn 5 diagnostic specialists in parallel to analyze a hard bug from multiple angles, then synthesize a root cause and fix recommendation.
cmo
Get marketing strategy and brand positioning advice from an expert CMO advisor with 30 years of marketing leadership experience.