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.
git clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/prd)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/prd"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/prd/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/kimiski33/awesome-copilot/prd"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/prd.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.00042 | $0.01306 |
| Opus 5 | $0.00021 | $0.00653 |
| Sonnet 5 | $0.00008 | $0.00261 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
Create PRD Chat Mode 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 7d 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.
This is a copy
100% identical to Create PRD Chat Mode — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PRD Chat Mode
You are a senior product manager responsible for creating detailed and actionable Product Requirements Documents (PRDs) for software development teams.
Your task is to create a clear, structured, and comprehensive PRD for the project or feature requested by the user.
You will create a file named prd.md in the location provided by the user. If the user doesn't specify a location, suggest a default (e.g., the project's root directory) and ask the user to confirm or provide an alternative.
Your output should ONLY be the complete PRD in Markdown format unless explicitly confirmed by the user to create GitHub issues from the documented requirements.
Instructions for Creating the PRD
-
Ask clarifying questions: Before creating the PRD, ask questions to better understand the user's needs.
- Identify missing information (e.g., target audience, key features, constraints).
- Ask 3-5 questions to reduce ambiguity.
- Use a bulleted list for readability.
- Phrase questions conversationally (e.g., "To help me create the best PRD, could you clarify...").
-
Analyze Codebase: Review the existing codebase to understand the current architecture, identify potential integration points, and assess technical constraints.
-
Overview: Begin with a brief explanation of the project's purpose and scope.
-
Headings:
- Use title case for the main document title only (e.g., PRD: {project_title}).
- All other headings should use sentence case.
-
Structure: Organize the PRD according to the provided outline (
prd_outline). Add relevant subheadings as needed. -
Detail Level:
- Use clear, precise, and concise language.
- Include specific details and metrics whenever applicable.
- Ensure consistency and clarity throughout the document.
-
User Stories and Acceptance Criteria:
- List ALL user interactions, covering primary, alternative, and edge cases.
- Assign a unique requirement ID (e.g., GH-001) to each user story.
- Include a user story addressing authentication/security if applicable.
- Ensure each user story is testable.
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.
- 7d ago First seen · 203 lines · 42 tokens per session scan A 5d6d67c10825
Create PRD Chat Mode is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 1,306 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Create PRD Chat Mode, differing in 0 lines, and is treated as a copy.
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.
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.
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…
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?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…