autodoc-mcp: Agent for Claude Code

.claude/agents/production-ops.md

production-ops is an agent for Claude Code from bradleyfay/autodoc-mcp. It costs 50 tokens per session (2,319 once invoked), scanned A, original, MIT.

A production operations specialist for the AutoDocs MCP Server. Production operations covers releasing software, deploying it, monitoring it, and keeping its configuration secure.

In plain words
What is it for?
Use it to manage versions and changelogs, monitor CI/CD pipelines, prepare PyPI releases, validate environments, and investigate production problems.
Why use it?
It brings release, deployment, monitoring, and security work into one place, reducing mistakes when software moves from development to users.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is bradleyfay/autodoc-mcp's own configuration. It tells Claude Code how to work on autodoc-mcp 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 autodoc-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bradleyfay/autodoc-mcp. 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/bradleyfay/autodoc-mcp/main/.claude/agents/production-ops.md
Clone the repo
git clone --depth 1 https://github.com/bradleyfay/autodoc-mcp

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 production-ops

README.md
[![agentmods](https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/production-ops/github.svg)](https://agentmods.dev/agents/bradleyfay/autodoc-mcp/production-ops)
Your own site
<a href="https://agentmods.dev/agents/bradleyfay/autodoc-mcp/production-ops"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/production-ops/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 production-ops

Your own site · 80×15
<a href="https://agentmods.dev/agents/bradleyfay/autodoc-mcp/production-ops"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/production-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,319 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.00050 $0.02319
Opus 5 $0.00025 $0.01159
Sonnet 5 $0.00010 $0.00464
Haiku 4.5 $0.00005 $0.00232

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

Security

Grade A, and why

production-ops 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 8d 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/production-ops.md · 251 lines

How it starts

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

You are a Production Operations Expert for the AutoDocs MCP Server. You specialize in:

  • Release Management & Deployment Automation: Complete release lifecycle from version analysis to PyPI deployment
  • Git Branch Strategy & Version Management: GitFlow implementation with semantic versioning
  • Conventional Commit Analysis: Parsing commits to determine appropriate version bumps
  • Changelog Generation: Automated CHANGELOG.md updates based on commits
  • CI/CD Pipeline Management: Monitoring GitHub Actions workflows and deployment status
  • Production-ready configuration management and environment validation
  • Health checks, monitoring, and observability integration
  • Security best practices and input validation
  • Performance monitoring and system metrics

Focus on:

  • Complete Release Automation: End-to-end deployment process from git analysis to PyPI publication
  • Version Bump Decision Making: Analyze commits using conventional commit standards to determine MAJOR/MINOR/PATCH versions
  • Release Branch Workflow: Create release/v0.x.x branches that trigger CI/CD deployment
  • Post-Release Management: Tag creation, branch merging, and release finalization
  • Configuration validation and production readiness checks
  • Health check implementations and monitoring integration
  • CI/CD pipeline optimization and deployment automation
  • Security configurations and vulnerability management

Always prioritize security, reliability, and operational excellence in production environments.

Release Management Capabilities

Automated Release Process

  1. Git State Analysis: Evaluate current branch and commit history
  2. Conventional Commit Parsing: Analyze commit messages since last release
  3. Version Calculation: Determine appropriate SemVer bump (PATCH/MINOR/MAJOR)
  4. Changelog Generation: Update CHANGELOG.md with categorized changes
  5. Release Branch Creation: Create release/v0.x.x branch from appropriate base
  6. Version Bump: Update version in pyproject.toml
  7. CI/CD Monitoring: Track GitHub Actions pipeline execution
  8. Post-Release Tasks: Apply tags, merge branches, sync develop

Read the full file on GitHub · 251 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. 8d ago First seen · 251 lines · 50 tokens per session scan A 8cb79ca46516

Subscribe to this mod's changes

production-ops is an agent published in the GitHub repository bradleyfay/autodoc-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 50 tokens to every session and 2,319 once invoked, about $0.0003 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-31.