operating-cadence

operating-cadence is a skill for Claude Code from cbrock84/headcount. It costs 95 tokens per session (775 once invoked), scanned A, original, MIT.

A structured way to handle an unexpected disruption that stops normal work, from declaring the incident through restoration, communication, and follow-up actions.

In plain words
What is it for?
Use it to assign an incident commander, coordinate recovery, communicate impact, keep a live timeline, and turn the review into completed improvements.
Why use it?
It reduces confusion and duplicated effort under time pressure by making ownership, communication, timelines, and stopping criteria explicit.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the operations plugin — 12 skills shipped together

Good fit Use it to assign an incident commander, coordinate recovery, communicate impact, keep…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cbrock84/headcount/operating-cadence
About the project

headcount is an organization of independently installable Claude Code plugins, each grouping skills for a department such as finance, security, or demand generation. Claude Code users install the departments they need and invoke their skills for specialized work; the catalogue entries are skills and related agent tooling from that organization.

cbrock84/headcount · 1,284 stars · on GitHub · cbrock84.github.io

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

Made for: Claude Code.

Or install operations, the plugin that ships this one along with the rest of its 12 skills.

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 operating-cadence

README.md
[![agentmods](https://agentmods.dev/badge/skills/cbrock84/headcount/operating-cadence.svg)](https://agentmods.dev/skills/cbrock84/headcount/operating-cadence)
Your own site
<a href="https://agentmods.dev/skills/cbrock84/headcount/operating-cadence"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/operating-cadence.svg" alt="Measured on agentmods" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 775 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.00095 $0.00775
Opus 5 $0.00048 $0.00387
Sonnet 5 $0.00019 $0.00155
Haiku 4.5 $0.00010 $0.00077

Measured 3d ago against content hash 802e2b7b9407, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

operating-cadence 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 3d 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.

plugins/operations/skills/operating-cadence/SKILL.md · 67 lines

How it starts

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

Operating cadence

Every organization has a cadence. Most have one that accumulated — a meeting added after each incident, none ever removed — rather than one that was designed. The symptom is familiar: full calendars, thorough reporting, and decisions that still take six weeks.

Give every recurring meeting a decision it exists to make

A review that only shares information is a document pretending to be a meeting. Before a meeting recurs, answer three questions: what decision does this forum make, who in the room can make it, and what would have to be true for the answer to be no.

If a forum has made no decision in a quarter, either it is the wrong forum or the decision is being made elsewhere. Both are worth knowing.

Separate the three time horizons, and do not let them merge

  • Weekly — execution. What is off track, what is blocking it, who is unblocking it by when. Short, operational, no strategy. Fifteen items at five minutes each, not five at fifteen.
  • Monthly — performance. Results against plan, with the variance explained by a driver rather than restated. This is where a trend gets caught while it is still cheap.
  • Quarterly — direction. Whether the plan is still the right plan, resource reallocation, and the deliberate stopping of things.

The common failure is a monthly review that fills with weekly firefighting, so nobody ever looks up. The fix is not discipline in the room; it is a functioning weekly meeting that leaves nothing urgent for the monthly one to absorb.

One set of numbers, owned by name

The same metric presented two ways in two forums will be argued about in both. Each metric needs a single definition, a single source, and one named owner who is accountable for the number rather than for the outcome it measures — those are different people surprisingly often, and the distinction stops reporting from becoming advocacy.

Publish the pack before the meeting and expect it read. A review that spends its first half being presented to has cut its own decision time in half.

Read the full file on GitHub · 67 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. 3d ago First seen · 67 lines · 95 tokens per session scan A 802e2b7b9407

Subscribe to this mod's changes

operating-cadence is a skill published in the GitHub repository cbrock84/headcount (1,284 stars, last pushed 4d ago), licensed MIT. It adds 95 tokens to every session and 775 once invoked, about $0.0005 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-09-03.

Related

Other skills, from other repositories

user-story-map

Build an interactive, drag-and-drop user story map so the user can re-slice work across release phases. Use when the user wants a story map, a phased roadmap, release slicing, a backbone/activities journey map, or to decide "which stories go in which phase" and move them around.

Cavalry-Collective/visual-stack · 65 tokens

diagnose-project

Diagnose .NET SDK, restore, build, test, package, target framework, F# compile-order, C# analyzer, and project-reference failures with concrete next checks.

gaelic-ghost/socket · 39 tokens

xcode-build-run-workflow

Guide build, run, preview-adjacent, workspace-inspection, diagnostics, toolchain, and guarded mutation work in existing Xcode-managed projects and workspaces. Use when Xcode-aware execution is needed and the task is primarily about build, run, or project-integrity work rather than testing.

gaelic-ghost/socket · 67 tokens

safari-mcp-workflow

Inspect a scoped live site in Safari through Safari Technology Preview's local MCP server. Use for Safari-specific DOM, console, network, screenshot, accessibility, performance, interaction, responsive, or print-media evidence.

gaelic-ghost/socket · 48 tokens

xcode-debugger-mcp-workflow

Diagnose a running Apple app through Xcode’s active LLDB debugging session and assess the experimental Xcode 27 lldb-mcp executable. Use when setting breakpoints, inspecting frames or variables, issuing LLDB commands, or distinguishing a usable Xcode debugger session from an unavailable standalone debugger MCP server.

gaelic-ghost/socket · 70 tokens

xcode-device-hub-workflow

Manage and validate simulated and physical Apple devices through Xcode Device Hub. Use when selecting or inspecting run destinations, interacting with an app, changing simulated-device environment settings, capturing screenshots or videos, pairing a device, or collecting diagnostics.

gaelic-ghost/socket · 54 tokens