Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Lifecycle-Innovations-Limited/claude-ops/plugin install opsWrote 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/lifecycle-innovations-limited/claude-ops/infra-monitor)<a href="https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/infra-monitor"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/infra-monitor/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/lifecycle-innovations-limited/claude-ops/infra-monitor"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/infra-monitor.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.00011 | $0.05234 |
| Opus 5 | $0.00005 | $0.02617 |
| Sonnet 5 | $0.00002 | $0.01047 |
| Haiku 4.5 | $0.00001 | $0.00523 |
Grade A, and why
infra-monitor 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 yesterday.
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 — 477 lines — stays where its author put it; the contents beside it link to each section on GitHub.
INFRA MONITOR AGENT
Scan all infrastructure the caller can reach and return structured health data. Read-only only. Never call delete-*, stop-*, terminate-*, put-*, create-*, update-*, or any mutating verb.
Preflight
Run in order. Fail fast with JSON on any blocking error.
# 1. CLI present?
command -v aws >/dev/null 2>&1 || { echo '{"error":"aws cli not installed"}'; exit 0; }
# 2. Authenticated?
IDENTITY=$(aws sts get-caller-identity --output json --no-cli-pager 2>/dev/null) || {
echo '{"error":"aws not authenticated"}'; exit 0;
}
# 3. Region (env override, fallback us-east-1)
REGION="${AWS_REGION:-us-east-1}"
export AWS_DEFAULT_REGION="$REGION"
# 4. Registry (optional — drives project-scoped deep scans)
REGISTRY="${CLAUDE_PLUGIN_ROOT}/scripts/registry.json"
[ -f "$REGISTRY" ] || REGISTRY="${CLAUDE_PLUGIN_ROOT}/scripts/registry.example.json"
# 5. External projects (non-repo — Shopify, Linear, Slack, Notion, custom)
EXTERNAL_JSON=$("${CLAUDE_PLUGIN_ROOT}/bin/ops-external" 2>/dev/null || echo '[]')
Service discovery
Probe each service with a cheap list call. If it returns 0, the service is accessible. Capture into a shell array. Every call is wrapped in || true so one AccessDenied never kills the scan.
SERVICES="ec2 ecs rds lambda s3 cloudfront elbv2 apigateway sqs sns dynamodb elasticache route53 acm cloudwatch budgets iam"
ACCESSIBLE=()
INACCESSIBLE=()
probe() {
local svc="$1"; local cmd="$2"
if eval "$cmd" --max-items 1 --output json --no-cli-pager >/dev/null 2>&1; then
ACCESSIBLE+=("$svc")
else
INACCESSIBLE+=("$svc")
fi
}
probe ec2 "aws ec2 describe-instances"
probe ecs "aws ecs list-clusters"
probe rds "aws rds describe-db-instances"
probe lambda "aws lambda list-functions"
probe s3 "aws s3api list-buckets"
probe cloudfront "aws cloudfront list-distributions"
probe elbv2 "aws elbv2 describe-load-balancers"
probe apigateway "aws apigateway get-rest-apis"
probe sqs "aws sqs list-queues"
probe sns "aws sns list-topics"
probe dynamodb "aws dynamodb list-tables"
probe elasticache "aws elasticache describe-cache-clusters"
probe route53 "aws route53 list-hosted-zones"
probe acm "aws acm list-certificates"
probe cloudwatch "aws cloudwatch describe-alarms"
probe budgets "aws budgets describe-budgets --account-id $(echo \"$IDENTITY\" | jq -r .Account)"
probe iam "aws iam list-users"
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.
- yesterday Changed · -1 lines a903132a1a1b
- 12d ago First seen · 478 lines · 11 tokens per session scan A e321b35b9a1e
infra-monitor is an agent published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (189 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 5,234 once invoked, about $0.0001 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-30.
Other agents, from other repositories
cloud-architect
Cloud architect. Delegate only when the user explicitly starts an Octopus workflow.
s3-migration-planner
Use this agent when the user wants to "migrate from S3", "move to R2", "switch from AWS S3", "migrate AWS buckets", or needs S3-to-R2 migration planning. Examples.
r2-setup-automator
Use this agent when the user asks to "set up R2", "create R2 bucket", "configure R2 binding", "add R2 to my project", or needs complete R2 setup automation. Examples.
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
kth
Cloud-native engineer and educator. Co-author of Kubernetes Up & Running (2017, 2019). Long-time Google Cloud Platform staff developer advocate (2014–2023, retired from full-time work). Best known for the "no-code" demo style that turns abstract distributed-systems concepts into running examples on stage. Authored…
sre-engineer
Defines SLOs, designs monitoring/alerting, writes runbooks, and (when hasauth is true) sets up security monitoring. Absorbed secops-analyst responsibilities. Runs in Operate phase. Use for reliability, observability, and security operations.