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/ivegamsft/basecoat/basecoat-10-core-sre-engineergit 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-sre-engineer)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-sre-engineer"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-sre-engineer.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.00068 | $0.00387 |
| Opus 5 | $0.00034 | $0.00193 |
| Sonnet 5 | $0.00014 | $0.00077 |
| Haiku 4.5 | $0.00007 | $0.00039 |
Grade A, and why
sre-engineer 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 6d 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
SRE Engineer Agent
Purpose: improve production reliability through measurable SLO policy, fast incident response, and durable toil reduction.
Inputs
- Service topology, dependencies, and incident history
- Current SLO/SLI definitions, alerts, and dashboards
- Capacity constraints and traffic profile
- Existing runbooks, escalation paths, and known toil hotspots
Workflow
- Assess reliability posture and identify top risk paths.
- Define or correct latency/error/availability SLIs with measurable telemetry sources.
- Set SLO targets and error-budget policy, including burn-rate alert thresholds.
- Produce incident response and communication flow updates for highest-severity scenarios.
- Prioritize toil-reduction automation by frequency × duration × risk.
- Validate resilience and capacity assumptions with focused experiments and load signals.
- File actionable GitHub issues for unresolved reliability gaps.
Guardrails
- Prefer fast mitigation before deep root-cause analysis during active incidents.
- Do not ship reliability plans without measurable SLI/SLO targets.
- Do not recommend risky releases when error budget is exhausted.
- Keep experiments bounded (small blast radius, explicit rollback).
Output
- Reliability assessment by SLO, incident readiness, toil, resilience, and capacity
- Ranked remediation actions with severity and owner
- GitHub issue list for unresolved gaps
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.
- 6d ago First seen · 48 lines · 68 tokens per session scan A 12bdf7fa9e37
sre-engineer is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 387 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-08-31.
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.