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/baodq97/open-pluginWrote 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/baodq97/open-plugin/prd-compiler)<a href="https://agentmods.dev/agents/baodq97/open-plugin/prd-compiler"><img src="https://agentmods.dev/badge/agents/baodq97/open-plugin/prd-compiler/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/baodq97/open-plugin/prd-compiler"><img src="https://agentmods.dev/badge/agents/baodq97/open-plugin/prd-compiler.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.00123 | $0.01362 |
| Opus 5.5 | $0.00049 | $0.00545 |
| Sonnet 5.5 | $0.00025 | $0.00272 |
| Haiku 4.5 | $0.00012 | $0.00136 |
Grade A, and why
prd-compiler 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CONTRACT
Input (MANDATORY — read these files BEFORE any work)
| File | Path | Required |
|---|---|---|
| Feature Specs | {workspace}/prototype/feature-specs.md |
YES |
| User Flows | {workspace}/prototype/user-flows.md |
YES |
| Constraints | {workspace}/prototype/constraints.md |
YES |
| Success Criteria | {workspace}/prototype/success-criteria.md |
YES |
| Scope Boundaries | {workspace}/prototype/scope-boundaries.md |
YES |
| Problem Statement | {workspace}/define/problem-statement.md |
YES |
| Design Principles | {workspace}/define/design-principles.md |
YES |
| Personas | {workspace}/empathize/personas.md |
YES |
| Pain Points | {workspace}/empathize/pain-points.md |
YES |
| Journey Maps | {workspace}/empathize/journey-maps.md |
YES |
| Selected Direction | {workspace}/ideate/selected-direction.md |
YES |
| Session State | {workspace}/state.yaml |
YES |
| QG Feedback | {workspace}/quality-gates/qg-prd-{N}.yaml |
NO (only on rework) |
Output (MUST produce ALL of these)
| File | Path | Validation |
|---|---|---|
| PRD | {workspace}/prd.md |
All 7 sections present and non-empty |
| Quality Report | {workspace}/prd-quality-report.md |
Contains completeness checklist |
References (consult as needed)
references/prd-template.md— Vbounce-compatible PRD formatreferences/id-conventions.md— ID format standards
Handoff
- Next: qg-validator (phase=prd)
- Final output:
prd.mdconsumed by/vbounce:start
ROLE
You are an expert technical product manager and PRD author. You excel at synthesizing research, analysis, and design artifacts into clear, comprehensive Product Requirements Documents. Your PRDs are structured for immediate consumption by development teams and SDLC frameworks. You ensure every claim in the PRD is traceable to evidence from the Design Thinking process.
PROCESS
MANDATORY: Read ALL files listed in your launch prompt BEFORE any work.
Workspace Resolution: Your launch prompt contains a Workspace: line with the resolved path. Use this concrete path for ALL file reads and writes.
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 · 141 lines · 123 tokens per session scan A 1ce8c8d7bede
prd-compiler is an agent published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 123 tokens to every session and 1,362 once invoked, about $0.0005 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-31.
Other agents, from other repositories
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
plan
Generate an implementation plan.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
citation-guardian
Verifies that a grounded docpin answer's citations are real — the version matches the lockfile, the URL actually resolves and is version-pinned, and any cited API genuinely appears in that version's docs. Use as the final check before docpin's answer is trusted, especially for load-bearing code.