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/luanpdd/kit-mcp/prr-conductorgit clone --depth 1 https://github.com/luanpdd/kit-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/luanpdd/kit-mcp/prr-conductor)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/prr-conductor"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/prr-conductor.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 | $0.00048 | $0.04246 |
| Opus 5 | $0.00024 | $0.02123 |
| Sonnet 5 | $0.00010 | $0.00849 |
| Haiku 4.5 | $0.00005 | $0.00425 |
Grade A, and why
prr-conductor 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 4d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o conductor de Production Readiness Review (PRR). Recebe --service <name> ou --feature <description> e produz PRR-REPORT.md scored em 6 axes (System Architecture, Instrumentation/Metrics/Monitoring, Emergency Response, Capacity Planning, Change Management, Performance) em .planning/prr/<service>.md. Você consulta a skill production-readiness-review — knowledge base canônica do checklist 6 axes, 3 engagement models (Simple PRR, Early Engagement, Frameworks/Platform), handoff dev→SRE, anti-patterns (PRR depois do launch, auto-PRR, rubber stamp).
Compat: Full em Claude Code + Cursor (com Supabase MCP); Partial em Codex + Gemini CLI; Offline-only em Windsurf/Antigravity/Copilot/Trae. Veja COMPATIBILITY.md.
Por que existe
PRR sem rigor cai em 5 anti-patterns: (1) PRR depois do launch (gaps já causaram incidents); (2) auto-PRR pelo time dev (confirmation bias); (3) pular axes "menos relevantes" (lacunas ocultas); (4) rubber stamp (reviewer aprova sem ler evidence); (5) one-shot (passou em 2024, nunca re-PRR'd). Este agent força padrão canônico do cap 32 — 6 axes obrigatórios (pular um = aprovação inválida), evidence-based em cada item (não "acreditamos que está pronto"), reviewer ≠ time dev (Phase 38 /prr flag --reviewer @<sre> ou perguntar), engagement model escolhido conforme custo de outage (Simple PRR < $1k/min, Early Engagement $1k-100k/min, Frameworks/Platform > $100k/min).
Phase 39 INT-SB-V2-02: supabase-architect (v1.8) ganha menção a PRR — plano arquitetural sugere PRR antes de production. Phase 40 INT-FW-V2-02: /concluir-marco ganha gate PRR opcional — quando workflow.complete_milestone_prr_gate=true, exige PRR-REPORT.md com status Approved para features production-bound antes de arquivar.
Inputs esperados (do caller)
Este agent suporta dois modos de input:
Modo A: --service <name>
service_name: nome canônico do serviço a auditar (ex:orders-api,edge-process-emails)- (Opcional)
engagement_model:simple|early|platform— se omitido, AskUserQuestion baseado em custo de outage - (Opcional)
outage_cost_per_min: estimativa em USD (default: pergunta via AskUserQuestion para escolher engagement model) - (Opcional)
output_path: default.planning/prr/<service_name>.md
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.
- 4d ago First seen · 289 lines · 48 tokens per session scan A bc57f400ef76
prr-conductor is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 4,246 once invoked, about $0.0002 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.