PluginBench
Skill
Pass
Audit score 90

enterprise-agent-ops

affaan-m/everything-claude-code

Operate long-lived agent workloads with observability, security boundaries, and lifecycle management.

What is enterprise-agent-ops?

This skill provides operational controls for cloud-hosted or continuously running agent systems. Use it when you need runtime lifecycle management, observability, safety controls, and change management beyond single CLI sessions.

  • Manage runtime lifecycle (start, pause, stop, restart) for long-lived agents
  • Implement observability through logs, metrics, and traces
  • Enforce safety controls including scopes, permissions, and kill switches
  • Execute change management with rollout, rollback, and audit trails
  • Apply least-privilege credentials and environment-level secret injection
  • Track key metrics: success rate, retries, recovery time, cost per task, and failure distribution

How to install enterprise-agent-ops

npx skills add https://github.com/affaan-m/everything-claude-code --skill enterprise-agent-ops
Prerequisites
  • Deployment infrastructure (PM2, systemd, container orchestrators, or CI/CD system)
  • Access to environment configuration and secret management
  • Monitoring and logging infrastructure for metrics and traces
Claude Code
Cursor
Windsurf
Cline

How to use enterprise-agent-ops

  1. 1.Install the skill using the provided npm command
  2. 2.Configure immutable deployment artifacts and environment-level secrets
  3. 3.Set hard timeout and retry budgets for your agent workloads
  4. 4.Establish baseline metrics tracking (success rate, retries, recovery time, cost)
  5. 5.Implement incident response procedures: freeze rollouts, capture traces, isolate failures, patch safely, and resume gradually
  6. 6.Integrate with your deployment system (PM2, systemd, or container orchestrator)

Use cases

Good for
  • Operating continuously running agent systems in production environments
  • Responding to failure spikes by freezing rollouts and isolating failing routes
  • Managing multi-environment deployments with audit requirements
  • Implementing incident response workflows with trace capture and regression testing
  • Enforcing security boundaries and permission controls across agent workloads
Who it's for
  • DevOps engineers managing production agent infrastructure
  • Platform teams building internal agent deployment systems
  • Organizations requiring audit trails and compliance controls for AI workloads
  • Teams operating multi-agent systems with high availability requirements

enterprise-agent-ops FAQ

What deployment systems does this skill support?

It pairs with PM2 workflows, systemd services, container orchestrators, and CI/CD gates.

What should I do when failure rates spike?

Follow the incident pattern: freeze new rollouts, capture representative traces, isolate the failing route, patch with the smallest safe change, run regression and security checks, then resume gradually.

What metrics should I track?

Monitor success rate, mean retries per task, time to recovery, cost per successful task, and failure class distribution.

How does this handle security?

It enforces least-privilege credentials, environment-level secret injection, immutable deployment artifacts, and maintains audit logs for high-risk actions.

Full instructions (SKILL.md)

Source of truth, from affaan-m/everything-claude-code.


name: enterprise-agent-ops description: Operate long-lived agent workloads with observability, security boundaries, and lifecycle management. metadata: origin: ECC

Enterprise Agent Ops

Use this skill for cloud-hosted or continuously running agent systems that need operational controls beyond single CLI sessions.

Operational Domains

  1. runtime lifecycle (start, pause, stop, restart)
  2. observability (logs, metrics, traces)
  3. safety controls (scopes, permissions, kill switches)
  4. change management (rollout, rollback, audit)

Baseline Controls

  • immutable deployment artifacts
  • least-privilege credentials
  • environment-level secret injection
  • hard timeout and retry budgets
  • audit log for high-risk actions

Metrics to Track

  • success rate
  • mean retries per task
  • time to recovery
  • cost per successful task
  • failure class distribution

Incident Pattern

When failure spikes:

  1. freeze new rollout
  2. capture representative traces
  3. isolate failing route
  4. patch with smallest safe change
  5. run regression + security checks
  6. resume gradually

Deployment Integrations

This skill pairs with:

  • PM2 workflows
  • systemd services
  • container orchestrators
  • CI/CD gates