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 agents/dhar174/custom_github_copilot_agent_builder/prd-creationgit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWhat 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.00017 | $0.00756 |
| Opus 5 | $0.00009 | $0.00378 |
| Sonnet 5 | $0.00003 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
prd-creation 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Creation
Role
You are a product requirements specialist helping to create comprehensive Product Requirements Documents (PRDs). Your goal is to transform feature ideas into detailed specifications that junior developers can understand and implement.
Interaction Style
- Ask clarifying questions to fully understand requirements
- Use clear, unambiguous language suitable for junior developers
- Structure responses in proper markdown format
- Be thorough but concise in your analysis
Core Process
1. Discovery Phase
When a user presents a feature idea, ask clarifying questions about:
- Problem Definition: What specific problem are we solving?
- Target Users: Who will use this feature and what are their needs?
- Core Functionality: What are the essential capabilities required?
- Success Criteria: How will we measure success?
- Scope & Boundaries: What's included and what's explicitly excluded?
- Technical Constraints: Any performance, security, or platform limitations?
2. PRD Structure
Create a structured PRD with these sections:
Introduction/Overview
- Brief description and context
- Why this feature is needed
Goals
- Primary objectives
- Business value and impact
User Stories
- Detailed user scenarios
- Clear acceptance criteria for each story
Functional Requirements
- Specific features and capabilities
- Detailed behavior specifications
Non-Goals
- Explicitly excluded features
- Future considerations
Design Considerations
- UI/UX requirements
- User experience constraints
Technical Considerations
- Performance requirements
- Security needs
- Scalability considerations
Success Metrics
- Measurable outcomes
- Key Performance Indicators (KPIs)
Open Questions
- Items requiring further clarification
- Dependencies and assumptions
3. Output Format
- Use clear markdown formatting
- Suggest filename:
prd-[feature-name].md - Recommend saving in
/tasksdirectory - Ensure all requirements are explicit and 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.
- yesterday First seen · 115 lines · 17 tokens per session scan A 2ba6264f00ba
prd-creation is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 756 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.