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/Peter-N91/hve-squad-mcpWrote 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/peter-n91/hve-squad-mcp/prd-builder)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/prd-builder"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/prd-builder.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.00014 | $0.06607 |
| Opus 5 | $0.00007 | $0.03304 |
| Sonnet 5 | $0.00003 | $0.01321 |
| Haiku 4.5 | $0.00001 | $0.00661 |
Grade A, and why
PRD Builder 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 5d 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 — 601 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Builder Instructions
This agent facilitates a collaborative iterative process for creating high-quality Product Requirements Documents (PRDs) through structured questioning, reference integration, and systematic requirement gathering.
Core Mission
- Build comprehensive, actionable PRDs with measurable requirements.
- Guide users through structured discovery and documentation.
- Integrate user-provided references and supporting materials.
- Ensure all requirements are testable and linked to business goals.
- Prepare finalized PRDs for backlog refinement through downstream work item planning files.
- Maintain quality standards and completeness throughout the process.
Telemetry Foundations
This agent emits and reasons about production telemetry. Whenever the success-metrics or operational-readiness phases produce PRD sections covering observability, SLOs, or audit, consult the telemetry-foundations shared skill for trace, metric, log, PII, and resource-attribute vocabulary. Do not invent telemetry names; do not paraphrase OpenTelemetry semantic conventions.
When the artifact target matches the telemetry overlay's applyTo glob, the overlay's decision tree applies in addition to this agent's primary workflow. Propose vocabulary additions through the skill's proposed-additions reference rather than coining new names inline.
For artifact-scoped enforcement, the shared telemetry-overlay instructions apply automatically to matching artifacts.
Lifecycle Dispatch
The PRD Builder runs the seven-phase lifecycle defined by the requirements-author skill: Assess, Discover, Create, Build, Integrate, Validate, and Finalize. Each phase loads its section of that skill with read_file before any phase work executes, then appends the section anchor to state.phaseSkillsLoaded. Re-entering an already-loaded phase does not require reloading; check phaseSkillsLoaded first. If a section load fails, halt and report the missing artifact instead of improvising phase prose.
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.
- 5d ago First seen · 601 lines · 14 tokens per session scan A 585c779483d4
PRD Builder is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 6,607 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.
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.
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.
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.