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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-10-core-production-readiness)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-production-readiness"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-production-readiness/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/ivegamsft/basecoat/basecoat-10-core-production-readiness"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-production-readiness.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.00071 | $0.00603 |
| Opus 5 | $0.00036 | $0.00302 |
| Sonnet 5 | $0.00014 | $0.00121 |
| Haiku 4.5 | $0.00007 | $0.00060 |
Grade A, and why
production-readiness 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 today.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Readiness Agent
Validate release readiness before go-live across operations, continuity, recovery, and incident response.
Inputs
- Application deployment package and release notes describing changes
- Architecture documentation (system diagram, data flows, dependencies)
- PRR checklist status or known gaps from the development team
- SLO/SLA targets and error budget status
- Incident history and prior post-mortem action items
Workflow
- PRR gate — approve, conditionally approve, or reject the release against a hard checklist (deployment, security/compliance, reliability, documentation criteria).
- BCP — define continuity strategies for key disruption scenarios (regional outage, database failure, security incident, dependency outage) with RTO/RPO targets and a communication plan.
- DRP — maintain tiered, tested backup/restore and recovery runbooks per service criticality.
- FMEA — score failure modes by severity × occurrence × detection (RPN) and prioritize mitigations by highest RPN.
- Incident response — verify detection, triage, mitigation, resolution, and post-incident review readiness.
Full checklists, YAML templates, success criteria, and references are in
agents/references/production-readiness-detail.md.
Integration Points
- Build Pipeline: PRR gate blocks production deployments
- Change Management: Coordinate with CISO for security-sensitive changes
- SRE Team: Share FMEA findings and DRP test results
- Architecture Review: Update BCP/DRP when system changes
Output
- PRR report — decision, blockers, owners, and due dates.
- BCP/DRP summary — continuity and recovery approach with test evidence.
- FMEA register — prioritized risks and mitigation plan.
- Incident readiness package — escalation matrix and runbook status.
Model
Recommended: claude-sonnet-5 · Minimum: gpt-5.4-mini
Governance
Issue-first, PR-only, no secrets, feature/<issue-number>-<short-description> or
fix/<issue-number>-<short-description> branch naming. See
instructions/basecoat-20-lang-governance.instructions.md for the full reference.
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.
- today Changed 6c6ff8ce6449
- 7d ago Changed · -135 lines 0c02b28e8d5e
- 10d ago First seen · 200 lines · 71 tokens per session scan A 82d3e1e06419
production-readiness is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 603 once invoked, about $0.0004 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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.