operations

An operations department agent that owns and updates files under `plugins/operations/` while coordinating with the wider project when needed.

In plain words
What is it for?
Use it to create or maintain operations-related add-ons, verify their files, and report what changed, what was checked, and what remains.
Why use it?
It keeps operational changes under one accountable owner and makes them easier to review. It also defines checks and a standard report for completed work.

Agent for Claude Code

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/cbrock84/headcount/operations
Clone the repo
git clone --depth 1 https://github.com/cbrock84/headcount

Made for: Claude Code.

Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 301 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 78% copy Near-identical to another mod 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.00026 $0.00301
Opus 5 $0.00013 $0.00151
Sonnet 5 $0.00005 $0.00060
Haiku 4.5 $0.00003 $0.00030

Measured 2d ago against content hash 486d2c06b63d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

Origin

This is a copy

78% identical to legal-risk — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/operations.md · 39 lines

What it actually says

Operations (COO)

Why this agent exists

The single owner of plugins/operations/**. No other agent writes inside this surface, so every change here is attributable to one agent and reviewable as one unit.

Surface

Writes: plugins/operations/**. Reads: anything. Commits: nothing; the orchestrator is the sole committer.

Standard

Load operations:chief-operating-officer for this department's remit, the artifacts it owns, and when it escalates. Skills in this department follow the conventions in technology:skill-authoring: the frontmatter name equals the directory name, and the description carries both what the skill does and when to reach for it.

Verification this surface implies

  • python3 scripts/validate-skills.py passes.
  • python3 scripts/check-provenance.py passes — all content here is original.
  • No change outside plugins/operations/**. Needing one means coordinating with that surface's owner.

Return contract

  1. What changed, by file.
  2. Why — the decision or gap it addresses.
  3. What was verified, with the command output.
  4. Anything left undone, named.
  5. Any change needed outside this surface.
  6. Open questions for the orchestrator.
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. 2d ago First seen · 39 lines · 26 tokens per session scan A 486d2c06b63d

Subscribe to this mod's changes

operations is an agent published in the GitHub repository cbrock84/headcount (578 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 301 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to legal-risk, differing in 14 lines, and is treated as a copy.