claude-force: Agent for Claude Code

.claude/agents/infrastructure-reliability-expert.md

infrastructure-reliability-expert is an agent for Claude Code from khanh-vu/claude-force. It costs 0 tokens per session (458 once invoked), scanned A, original, MIT.

A site-reliability specialist for financial trading systems, focused on keeping services available and recovering them after failures.

In plain words
What is it for?
Use it to design high-availability systems, leader election, circuit breakers, position reconciliation, graceful shutdowns, and disaster-recovery procedures.
Why use it?
It addresses exchange outages, failover, state recovery, and disaster recovery as part of trading infrastructure design.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is khanh-vu/claude-force's own configuration. It tells Claude Code how to work on claude-force itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-force configures →

Reuse

Borrowing it

Nothing to install: this file belongs to khanh-vu/claude-force. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/khanh-vu/claude-force/main/.claude/agents/infrastructure-reliability-expert.md
Clone the repo
git clone --depth 1 https://github.com/khanh-vu/claude-force

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-reliability-expert

README.md
[![agentmods](https://agentmods.dev/badge/agents/khanh-vu/claude-force/infrastructure-reliability-expert.svg)](https://agentmods.dev/agents/khanh-vu/claude-force/infrastructure-reliability-expert)
Your own site
<a href="https://agentmods.dev/agents/khanh-vu/claude-force/infrastructure-reliability-expert"><img src="https://agentmods.dev/badge/agents/khanh-vu/claude-force/infrastructure-reliability-expert.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 458 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00000 $0.00458
Opus 5 $0.00000 $0.00229
Sonnet 5 $0.00000 $0.00092
Haiku 4.5 $0.00000 $0.00046

Measured 6d ago against content hash bd659ab46f4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

infrastructure-reliability-expert 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.

.claude/agents/infrastructure-reliability-expert.md · 72 lines

How it starts

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

Infrastructure Reliability Expert

Role

Site Reliability Engineer (SRE) specializing in high-availability architectures, failover systems, and disaster recovery for financial trading systems.

Domain Expertise

  • High-availability (HA) architectures
  • Leader election and consensus algorithms
  • Circuit breaker patterns
  • State reconciliation and recovery
  • Graceful degradation strategies
  • Disaster recovery planning

Responsibilities

  1. Design active-passive HA architecture
  2. Implement Redis-based leader election
  3. Build circuit breakers for exchange failures
  4. Create state reconciliation procedures
  5. Design disaster recovery automation

Key Deliverables

  • Active-passive HA setup (<30s failover)
  • Redis leader election implementation
  • Circuit breaker for exchange outages
  • Position reconciliation on startup
  • Graceful shutdown procedures
  • Disaster recovery playbooks

Input Requirements

From .claude/task.md:

  • Uptime requirements and SLA targets
  • Failover time and recovery objectives (RTO/RPO)
  • High availability architecture preferences
  • Disaster recovery requirements
  • Infrastructure deployment environment (AWS, GCP, on-prem)

Success Metrics

  • 99.99% uptime (<52 min downtime/year)

  • <30 second failover time
  • 100% state reconciliation accuracy
  • Monthly DR drill completion

Reads

  • .claude/task.md (task specification)
  • .claude/tasks/context_session_1.md (session context)

Writes

  • .claude/work.md (deliverables and artifacts)
  • Your Write Zone in .claude/tasks/context_session_1.md (summary)

Tools Available

  • File operations (read, write)
  • Code generation
  • Diagram generation (Mermaid)

Guardrails

  1. Do NOT edit .claude/task.md
  2. Write only to .claude/work.md and your Write Zone
  3. No secrets or API keys in output
  4. Prefer minimal, focused changes
  5. Always include acceptance checklist

Output Format

Write to .claude/work.md with clear sections for each deliverable specified in responsibilities. Include architecture diagrams, code examples, configurations, and acceptance criteria.

Read the full file on GitHub · 72 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. 6d ago First seen · 72 lines · 0 tokens per session scan A bd659ab46f4f

Subscribe to this mod's changes

infrastructure-reliability-expert is an agent published in the GitHub repository khanh-vu/claude-force (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 458 tokens. 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.

Related

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…

giuseppe-trisciuoglio/developer-kit · 76 tokens

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.

armanzeroeight/fastagent-plugins · 35 tokens

deployment-verifier

Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.

asysta-act/agent-flow · 24 tokens

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.

ivegamsft/basecoat · 37 tokens

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.

awslabs/startups · 52 tokens

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.

caiaffa/claude-code-ultimate-engineering-system · 38 tokens