operate-agent

A production-operations tool for deployed software. It covers deployment, monitoring, logs, incidents, scaling, security checks, and infrastructure costs.

In plain words
What is it for?
Use it to coordinate blue-green, canary, or rolling deployments; monitor system health; analyze logs; manage incidents; scale resources; scan for vulnerabilities; validate compliance; and review performance or infrastructure costs.
Why use it?
It brings routine checks and responses into one place, helping teams detect problems and manage running systems. Production means the live environment used by real users.

Agent

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/itdojp/ae-framework/operate-agent
Clone the repo
git clone --depth 1 https://github.com/itdojp/ae-framework
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 5,349 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 $0.00000 $0.05349
Opus 5 $0.00000 $0.02674
Sonnet 5 $0.00000 $0.01070
Haiku 4.5 $0.00000 $0.00535

Measured yesterday against content hash cc4d1dfe8f00, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

operate-agent 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.

docs/legacy/agents/operate-agent.md · 660 lines

How it starts

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

Operate Agent - Phase 6 of ae-framework

🌍 Language / 言語: English | 日本語


English

The Operate Agent is the final phase in the ae-framework's 6-phase cycle (Intent→Formal→Tests→Code→Verify→Operate). It handles production operations, monitoring, and optimization to ensure deployed systems run reliably, efficiently, and securely.

Overview

The Operate Agent provides comprehensive production operations capabilities including:

  • Deployment Orchestration: CI/CD integration with blue-green, canary, and rolling deployment strategies
  • Infrastructure Monitoring: Real-time health checks and alerting across all system endpoints
  • Performance Optimization: Automated performance analysis and tuning recommendations
  • Log Analysis: Intelligent log aggregation, pattern detection, and anomaly identification
  • Incident Management: Complete incident lifecycle management from creation to resolution
  • Resource Scaling: Dynamic auto-scaling based on performance metrics and demand
  • Security Monitoring: Vulnerability scanning and compliance framework validation
  • Cost Optimization: Infrastructure cost analysis and optimization recommendations
  • Chaos Engineering: Controlled resilience testing through chaos experiments
  • SLO/SLA Tracking: Service level objective monitoring and compliance reporting

Architecture

Core Components

src/agents/operate-agent.ts        # Core agent implementation
src/mcp-server/operate-server.ts   # MCP server wrapper

Key Classes

  • OperateAgent: Main agent class providing all operational capabilities
  • OperateServer: MCP server providing tool interfaces for agent operations

Configuration

The Operate Agent is configured through the OperateAgentConfig interface:

interface OperateAgentConfig {
  deploymentConfig: DeploymentConfig;
  monitoringConfig: MonitoringConfig;
  alertingConfig: AlertingConfig;
  scalingConfig: ScalingConfig;
  securityConfig: SecurityConfig;
  costConfig: CostConfig;
  sloConfig: SloConfig;
  chaosConfig: ChaosConfig;
}

Read the full file on GitHub · 660 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. yesterday First seen · 660 lines · 0 tokens per session scan A cc4d1dfe8f00

Subscribe to this mod's changes

operate-agent is an agent published in the GitHub repository itdojp/ae-framework (2 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 5,349 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

playwright-test-generator

Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…

SigNoz/signoz · 0 tokens

playwright-test-healer

Use this agent to debug and fix failing SigNoz E2E Playwright tests. Examples — Context: A spec is red. user: 'tests/e2e/tests/dashboards/list.spec.ts is failing, fix it' assistant: 'Using the healer agent to debug each failing scenario and adjust the spec.' Context: After a frontend change a previously-green spec…

SigNoz/signoz · 0 tokens

playwright-test-planner

Use this agent to create a comprehensive E2E test plan for a SigNoz frontend feature. Examples — Context: A new feature has shipped and we need test coverage. user: 'Plan E2E tests for the alerts list page' assistant: 'I'll use the planner agent to read the relevant frontend source, navigate the page in a real…

SigNoz/signoz · 0 tokens

codex

Production OpenAI-Codex-capable rootfs/initramfs.

the-void-ia/void-box · 0 tokens

claude

Production Claude-capable rootfs/initramfs.

the-void-ia/void-box · 0 tokens

doc-style

Markdown documentation prose — RFCs, ADRs, files under docs/, and READMEs — follows the same one-paragraph-per-line rule as commit messages. Write each paragraph on a single line; do not hard-wrap prose to a fixed column. The renderer reflows it to the reader's display width, whereas manual mid-paragraph line breaks…

the-void-ia/void-box · 0 tokens