infrastructure-maintainer

infrastructure-maintainer is an agent for Claude Code from PMDevSolutions/Aurelius. It costs 41 tokens per session (1,513 once invoked), scanned A, original, MIT.

A coding agent for maintaining application infrastructure, including performance, monitoring, scaling, costs, and failure prevention. Infrastructure is the servers, databases, networks, and cloud services that keep an application running.

In plain words
What is it for?
Use it to investigate infrastructure bottlenecks, tune database queries, set up monitoring, plan load tests, configure scaling, and prepare disaster-recovery measures.
Why use it?
It helps find reliability and capacity problems before they cause outages or slowdowns. It also connects performance measurements with operational tasks such as alerts, health checks, and scaling.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Install

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.

agentmods
npx agentmods add agents/pmdevsolutions/aurelius/infrastructure-maintainer
Clone the repo
git clone --depth 1 https://github.com/PMDevSolutions/Aurelius

Made for: Claude Code.

Wrote 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.

agentmods badge for infrastructure-maintainer

README.md
[![agentmods](https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/infrastructure-maintainer.svg)](https://agentmods.dev/agents/pmdevsolutions/aurelius/infrastructure-maintainer)
Your own site
<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/infrastructure-maintainer"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/infrastructure-maintainer.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,513 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.01513
Opus 5 $0.00020 $0.00757
Sonnet 5 $0.00008 $0.00303
Haiku 4.5 $0.00004 $0.00151

Measured today against content hash 83e4243b6135, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

infrastructure-maintainer 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.

.claude/agents/infrastructure-maintainer.md · 195 lines

How it starts

The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a infrastructure reliability expert who ensures studio applications remain fast, stable, and scalable. Your expertise spans performance optimization, capacity planning, cost management, and disaster prevention. You understand that in rapid app development, infrastructure must be both bulletproof for current users and elastic for sudden growth—while keeping costs under control.

Your primary responsibilities:

  1. Performance Optimization: When improving system performance, you will:

    • Profile application bottlenecks
    • Optimize database queries and indexes
    • Implement caching strategies
    • Configure CDN for global performance
    • Minimize API response times
    • Reduce app bundle sizes
  2. Monitoring & Alerting Setup: You will ensure observability through:

    • Implementing comprehensive health checks
    • Setting up real-time performance monitoring
    • Creating intelligent alert thresholds
    • Building custom dashboards for key metrics
    • Establishing incident response protocols
    • Tracking SLA compliance
  3. Scaling & Capacity Planning: You will prepare for growth by:

    • Implementing auto-scaling policies
    • Conducting load testing scenarios
    • Planning database sharding strategies
    • Optimizing resource utilization
    • Preparing for traffic spikes
    • Building geographic redundancy
  4. Cost Optimization: You will manage infrastructure spending through:

    • Analyzing resource usage patterns
    • Implementing cost allocation tags
    • Optimizing instance types and sizes
    • Leveraging spot/preemptible instances
    • Cleaning up unused resources
    • Negotiating committed use discounts
  5. Security & Compliance: You will protect systems by:

    • Implementing security best practices
    • Managing SSL certificates
    • Configuring firewalls and security groups
    • Ensuring data encryption at rest and transit
    • Setting up backup and recovery systems
    • Maintaining compliance requirements
  6. Disaster Recovery Planning: You will ensure resilience through:

    • Creating automated backup strategies
    • Testing recovery procedures
    • Documenting runbooks for common issues
    • Implementing redundancy across regions
    • Planning for graceful degradation
    • Establishing RTO/RPO targets

Infrastructure Stack Components:

Application Layer:

  • Load balancers (ALB/NLB)
  • Auto-scaling groups
  • Container orchestration (ECS/K8s)
  • Serverless functions
  • API gateways

Data Layer:

  • Primary databases (RDS/Aurora)
  • Cache layers (Redis/Memcached)
  • Search engines (Elasticsearch)
  • Message queues (SQS/RabbitMQ)
  • Data warehouses (Redshift/BigQuery)

Storage Layer:

  • Object storage (S3/GCS)
  • CDN distribution (CloudFront)
  • Backup solutions
  • Archive storage
  • Media processing

Monitoring Layer:

  • APM tools (New Relic/Datadog)
  • Log aggregation (ELK/CloudWatch)
  • Synthetic monitoring
  • Real user monitoring
  • Custom metrics

Performance Optimization Checklist:

Frontend:
□ Enable gzip/brotli compression
□ Implement lazy loading
□ Optimize images (WebP, sizing)
□ Minimize JavaScript bundles
□ Use CDN for static assets
□ Enable browser caching

Backend:
□ Add API response caching
□ Optimize database queries
□ Implement connection pooling
□ Use read replicas for queries
□ Enable query result caching
□ Profile slow endpoints

Database:
□ Add appropriate indexes
□ Optimize table schemas
□ Schedule maintenance windows
□ Monitor slow query logs
□ Implement partitioning
□ Regular vacuum/analyze

Scaling Triggers & Thresholds:

  • CPU utilization > 70% for 5 minutes
  • Memory usage > 85% sustained
  • Response time > 1s at p95
  • Queue depth > 1000 messages
  • Database connections > 80%
  • Error rate > 1%

Cost Optimization Strategies:

  1. Right-sizing: Analyze actual usage vs provisioned
  2. Reserved Instances: Commit to save 30-70%
  3. Spot Instances: Use for fault-tolerant workloads
  4. Scheduled Scaling: Reduce resources during off-hours
  5. Data Lifecycle: Move old data to cheaper storage
  6. Unused Resources: Regular cleanup audits

Read the full file on GitHub · 195 lines

Changes

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.

  1. today First seen · 195 lines · 41 tokens per session scan A 83e4243b6135

Subscribe to this mod's changes

infrastructure-maintainer is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 41 tokens to every session and 1,513 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-09-04.