agent-production-operations

agent-production-operations is a skill for Claude Code, Codex from magnus919/agent-skills. It costs 82 tokens per session (3,380 once invoked), scanned A, original, MIT.

A set of operating rules for running an already-tested software agent in production. It covers controlled releases, monitoring, limits, fallbacks, human escalation, and disabling the agent.

In plain words
What is it for?
Use it to roll out an agent gradually, monitor its tool use, set cost or response-time limits, handle failures, and feed production incidents back into testing.
Why use it?
It helps manage the risks of giving an agent tools and authority after testing. It keeps costs, response time, failures, and unsafe actions under control.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

Good fit Use it to roll out an agent gradually, monitor its tool use, set cost or response-time limits, handle failures, and feed production incidents back into testing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/magnus919/agent-skills/agent-production-operations
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.

Any agent
npx skills add magnus919/agent-skills --skill agent-production-operations
Clone the repo
git clone --depth 1 https://github.com/magnus919/agent-skills

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin agent-production-operations/plugin install agent-production-operations after adding the marketplace above.

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 agent-production-operations

README.md
[![agentmods](https://agentmods.dev/badge/skills/magnus919/agent-skills/agent-production-operations/github.svg)](https://agentmods.dev/skills/magnus919/agent-skills/agent-production-operations)
Your own site
<a href="https://agentmods.dev/skills/magnus919/agent-skills/agent-production-operations"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/agent-production-operations/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for agent-production-operations

Your own site · 80×15
<a href="https://agentmods.dev/skills/magnus919/agent-skills/agent-production-operations"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/agent-production-operations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,380 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 74
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
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.00082 $0.03380
Opus 5 $0.00041 $0.01690
Sonnet 5 $0.00016 $0.00676
Haiku 4.5 $0.00008 $0.00338

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

Security

Grade A, and why

agent-production-operations 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 11d 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.

agent-production-operations/SKILL.md · 268 lines

How it starts

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

agent-production-operations

A runtime control plane for taking an evaluated agent with tools and authority into controlled production operation. This bundle bridges the gap between passing evaluations and safe production use: it defines how an agent is versioned, rolled out, monitored, constrained, escalated, and disabled — and how production evidence feeds back into evaluation and release decisions.

The bundle does not build agents, design evaluations, run release pipelines, or own infrastructure. It composes those concerns from existing specialist skills and owns only the runtime control decisions between them.

When to load this

Load this bundle when you are operating an agent that:

  • Has passed evaluation and is cleared for production consideration.
  • Has tools with side effects and delegated authority that must be gated.
  • Needs a staged rollout with progressive authority expansion.
  • Must be monitored for cost, latency, tool health, and authority usage in production.
  • Requires a defined fallback, escalation, and disablement path.
  • Should feed production traces and incidents back into evaluation cases and release-gate updates.

When not to use

Do not load this bundle for:

  • Building or designing an agent from scratch — route to the appropriate framework skill (LangGraph, CrewAI, AutoGen, etc.).
  • Designing agent evaluations or observability — route to agent-evals-and-observability.
  • General release engineering (CI/CD pipelines, artifact promotion) — route to release-engineering.
  • General site reliability engineering (incident response, SLO definition, error budgets) — route to site-reliability-engineering.
  • General security engineering (threat modeling, vulnerability assessment) — route to secure-software-engineering.
  • General platform infrastructure (compute, networking, storage) — route to platform-engineering.
  • Performing a production-readiness review — route to production-readiness; this bundle consumes readiness outcomes, it does not produce them.
  • Conducting an incident postmortem — route to incident-learning; this bundle consumes incident records as escalation and feedback inputs.

Read the full file on GitHub · 268 lines

Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 268 lines · 82 tokens per session scan A 5eb44374faa6

Subscribe to this mod's changes

agent-production-operations is a skill published in the GitHub repository magnus919/agent-skills (76 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 3,380 once invoked, about $0.0004 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-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens