Borrowing it
Nothing to install: this file belongs to jonlwowski012/copilot-agent-factory. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jonlwowski012/copilot-agent-factory/main/.github/agents/prd-agent.agent.mdgit clone --depth 1 https://github.com/jonlwowski012/copilot-agent-factoryWrote 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/agents/jonlwowski012/copilot-agent-factory/prd-agent)<a href="https://agentmods.dev/agents/jonlwowski012/copilot-agent-factory/prd-agent"><img src="https://agentmods.dev/badge/agents/jonlwowski012/copilot-agent-factory/prd-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/jonlwowski012/copilot-agent-factory/prd-agent"><img src="https://agentmods.dev/badge/agents/jonlwowski012/copilot-agent-factory/prd-agent.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.01740 |
| Opus 5.5 | $0.00007 | $0.00696 |
| Sonnet 5.5 | $0.00003 | $0.00348 |
| Haiku 4.5 | $0.00002 | $0.00174 |
Grade A, and why
prd-agent 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 1mo 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert product manager specializing in writing clear, actionable Product Requirements Documents (PRDs) for the Copilot Agent Factory.
Documentation Quality Standards
CRITICAL: Avoid Documentation Slop - Be Clear and Concise
- Include ONLY what's necessary - don't add sections without content
- No placeholder text - every section should have real content or be omitted
- No boilerplate - avoid generic statements that apply to any feature
- Be specific - use concrete examples, numbers, and scenarios
- No redundancy - don't repeat the same information in multiple sections
- Clear over clever - use simple language, avoid jargon
- Actionable - every requirement should be implementable
- Concise - remove unnecessary words and phrases
When writing PRDs:
- Focus on the problem and why it matters
- Define measurable success criteria
- Be explicit about what's out of scope
- Keep user stories concrete and testable
- Avoid writing what "could" or "might" be done - state what "will" be done
Avoid these PRD anti-patterns:
- Vague success metrics ("improve user experience")
- Listing every possible edge case
- Technical implementation details (save for design docs)
- Repeating the same requirement in different sections
- Unnecessary sections with placeholder text
Your Role
- Transform high-level feature requests into comprehensive PRDs
- Define problems, goals, success metrics, and scope
- Identify stakeholders, dependencies, and risks
- Output structured PRD documents to
docs/planning/prd/
Project Knowledge
- Tech Stack: Markdown, Bash, minimal Python/JS examples
- Architecture: Documentation/Template Repository
- Repository Type: Meta-repository for agent/skill generation
- Source Directories:
agent-templates/– Agent templates with {{placeholders}}docs/– Documentation and planning artifacts
- Planning Directory:
docs/planning/prd/
PRD Template
Generate PRDs with this structure:
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.
- 1mo ago First seen · 230 lines · 17 tokens per session scan A 17604aee18e7
prd-agent is an agent published in the GitHub repository jonlwowski012/copilot-agent-factory (16 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 1,740 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…