enterprise-agent-ops

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

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Femad-6/my-skills --skill enterprise-agent-ops-femad-6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enterprise-agent-ops
Source: https://github.com/Femad-6/my-skills/tree/main/.github/skills/enterprise-agent-ops
Command: npx skills add https://github.com/Femad-6/my-skills --skill enterprise-agent-ops-femad-6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running AI agents as continuously hosted services introduces operational risks that single CLI sessions never face: uncontrolled restarts, missing audit trails, silent failure spikes, and unbounded costs. This Skill provides the operational controls needed to run agent workloads safely in production. ## Core Features & Use Cases - Lifecycle Management: Standardized start, pause, stop, and restart procedures for long-running agent processes across PM2, systemd, and container orchestrators. - Observability Baselines: Defines the metrics that matter for agent operations, including success rate, mean retries per task, time to recovery, cost per successful task, and failure class distribution. - Safety Controls: Enforces least-privilege credentials, environment-level secret injection, hard timeout and retry budgets, kill switches, and audit logs for high-risk actions. - Incident Response Pattern: A six-step failure-spike playbook covering rollout freeze, trace capture, route isolation, minimal patching, regression and security checks, and gradual resumption. - Use Case: A team deploying a customer-support agent as a systemd service uses this Skill to set retry budgets, wire audit logging for high-risk actions, and follow the incident pattern when failure rates spike after a model update. ## Quick Start Ask the agent to design an operations plan with observability metrics, safety controls, and an incident response procedure for your continuously running agent deployment.

Frequently Asked Questions about enterprise-agent-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I operate long-running AI agents in production?

Long-running agents need lifecycle controls for start, pause, stop, and restart, plus observability through logs, metrics, and traces. Pair the workload with PM2, systemd, or a container orchestrator and enforce timeout and retry budgets.

What metrics should I track for agent workloads?

Track success rate, mean retries per task, time to recovery, cost per successful task, and failure class distribution. These five metrics expose reliability problems and cost drift before they become incidents.

How do I respond to failure spikes in an agent deployment?

Freeze new rollouts, capture representative traces, isolate the failing route, and patch with the smallest safe change. Then run regression and security checks before resuming traffic gradually.

What security controls do hosted agents need?

Use immutable deployment artifacts, least-privilege credentials, and environment-level secret injection. Add hard timeout and retry budgets plus an audit log for high-risk actions to contain blast radius.

Can I use this with systemd or PM2 services?

Yes, the operational patterns pair directly with PM2 workflows, systemd services, container orchestrators, and CI/CD gates. The lifecycle and rollback controls map onto whichever process manager hosts the agent.