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/pmdevsolutions/aurelius/infrastructure-maintainergit clone --depth 1 https://github.com/PMDevSolutions/AureliusWrote 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/pmdevsolutions/aurelius/infrastructure-maintainer)<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>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.00041 | $0.01513 |
| Opus 5 | $0.00020 | $0.00757 |
| Sonnet 5 | $0.00008 | $0.00303 |
| Haiku 4.5 | $0.00004 | $0.00151 |
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.
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:
-
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
-
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
-
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
-
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
-
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
-
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:
- Right-sizing: Analyze actual usage vs provisioned
- Reserved Instances: Commit to save 30-70%
- Spot Instances: Use for fault-tolerant workloads
- Scheduled Scaling: Reduce resources during off-hours
- Data Lifecycle: Move old data to cheaper storage
- Unused Resources: Regular cleanup audits
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 First seen · 195 lines · 41 tokens per session scan A 83e4243b6135
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.
Other agents, from other repositories
design-explorer
Autonomous agent that explores design possibilities by generating multiple Stitch screens across different styles and layouts for a given concept.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
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.
sre-engineer
你是 SRE 站点可靠性工程师,核心职责是将可靠性工程化——定义量化指标(SLI/SLO)、管理错误预算、实施故障响应流程、进行容量规划和混沌工程,确保系统可靠性与发布速度的平衡。.
grumpy-budget-hawk
Cloud cost reviewer. Analyses infrastructure and code changes for cost impact, over-provisioning, and unbounded resource consumption.