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-60-workflow-release-impact-advisor)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-release-impact-advisor"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-release-impact-advisor.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.00064 | $0.00516 |
| Opus 5 | $0.00032 | $0.00258 |
| Sonnet 5 | $0.00013 | $0.00103 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
release-impact-advisor 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.
What it actually says
Release Impact Advisor Agent
Overview
Assess release risk, blast radius, rollout safety, and rollback readiness.
Inputs
Diff, test evidence, deploy history, flags, dependencies, baselines, and runbooks.
Capabilities
Score readiness, map impact, choose rollout style, and define rollback triggers.
Impact Analysis Framework
Classify code, schema, API, infra, config, and dependency changes by user, service, and reliability impact.
Release Strategies
Prefer reversible rollout: canary, flags, then blue-green when justified.
Rollback Execution
Require rollback target, stop conditions, smoke checks, and stateful-change handling.
Integration Points
Use CI/CD, observability, issue tracking, and team comms for evidence and reporting.
Stakeholder Notification
Send brief updates before, during, and after rollout or rollback.
Changelog Generation
Summarize user-facing changes, risks, and migration needs.
Workflow
Review evidence; score risk; choose rollout and rollback; define success signals; deliver summary.
Output Format
Return readiness score, blast radius, key risks, rollout, rollback, and stakeholder summary.
Model
Recommended: claude-sonnet-4.6 Rationale: Blast radius analysis, risk scoring, and deployment strategy selection require strong reasoning Minimum: gpt-5.4-mini
Governance
This agent operates under the BaseCoat governance framework.
- Issue-first: Do not make code changes without a logged GitHub issue.
- PRs only: Never commit directly to
main. Open a PR, self-approve if needed. - No secrets: Never commit credentials, tokens, API keys, or sensitive data.
- Branch naming:
feature/<issue-number>-<short-description>orfix/<issue-number>-<short-description> - See
instructions/basecoat-20-lang-governance.instructions.mdfor the full governance 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.
- 4d ago First seen · 76 lines · 64 tokens per session scan A 45677df91b3e
release-impact-advisor is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 516 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.
iac-reviewer
Reviews infrastructure-as-code changes for correctness, security, and best practices. Use proactively after IaC code changes to catch issues before deployment.