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.
npx skills add alexclowe/awesome-claude-cowork-plugins --skill operating-rhythmgit clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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.
[](https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/operating-rhythm)<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/operating-rhythm"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/operating-rhythm/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.
<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/operating-rhythm"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/operating-rhythm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00029 | $0.00547 |
| Opus 5.5 | $0.00012 | $0.00219 |
| Sonnet 5.5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
operating-rhythm 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 22d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- operating-rhythm — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You understand how a one-person company keeps its week from being eaten by the inbox. When the user is planning their week, reviewing what shipped, writing an update, or deciding what to work on next, apply this knowledge automatically.
The weekly loop
- Friday: retro. Shipped, blocked, learned, follow-ups owed. First person, short, no motivational filler. Metrics only if the user supplied them.
- Friday or Monday: plan. Exactly three bets for the week. Each bet has:
- a done-check — something that can be answered yes or no on Friday afternoon
- a riskiest assumption — the thing that, if false, kills the bet
- an hours estimate and a specific calendar block (day plus time range)
- A "not doing" list with a reason for each item. Things without a reason drift back into the week.
- Hours ceiling: the three bets total 25 hours or fewer. A plan that doesn't fit loses a bet; it doesn't get squeezed.
The monthly loop
- An investor-style update, written even when there are no investors: metrics (this month vs last), what shipped, what didn't ship and the honest reason, next month's top three, the thing keeping me up at night, and specific asks.
- Candor beats polish. A monthly update that admits the risk builds more trust than one that only reports wins.
- Specific asks ("an intro to someone who runs operations at a 20-location clinic group") get answered; vague ones ("intros to anyone in healthcare") don't.
Metric discipline
- One primary number the founder watches every week (MRR, weekly active users, trials started, whatever fits the stage).
- Never invent, estimate, or extrapolate a metric the user didn't give. Missing numbers become bracketed placeholders like [MRR — add this month's figure].
- Percent changes only when both values are known.
Customer evidence
- Five conversations are an early signal, not a conclusion. Say so.
- Attribute every quote to its interview; never paraphrase inside quotation marks.
- Feature requests from people outside the target customer are noise until proven otherwise.
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.
- 22d ago First seen · 43 lines · 29 tokens per session scan A c861b4535c44
operating-rhythm is a skill published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 547 once invoked, about $0.0001 per session on Opus 5.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-25.
Other skills, from other repositories
coordinate-meeting
Coordinates project meetings: generates a structured agenda, creates a Google Calendar event, and prepares a protocol template. Covers 5 meeting types across the full project lifecycle — tasks #6, #15, #17, #20, #26. Meeting types: Go/No-Go (Phase 1, #6), Client Demo (Phase 3, #15), Sprint Planning (Phase 4, #17)…
generate-approval-letter
Generates an approval-letter.md email body and an email-tpl-approval.md template for Phase 2 — Planning. Reads project-plan.md, project-budget.xlsx, and resource-plan.md to compose a formal approval request addressed to all Approver-level stakeholders from stakeholder-map.md. Produces two artifacts: the letter email…
generate-budget
Generates a detailed project budget (project-budget.xlsx) for Phase 2 — Planning, based on preliminary-estimate.xlsx and resource-plan.md. Produces a single baseline scenario structured by project phases and cost categories (team, infrastructure, GTM), with a contingency reserve as a separate line item. Covers task #9…
generate-change-impact
Generates a change impact assessment file (change-impact-CR-001.xlsx) for Phase 4 — Development. PM describes a scope change request; the agent classifies the change (scope / budget / timeline / resource), analyzes impact on project-plan.md and project-budget.xlsx, calculates timeline delta, budget delta, and risk…
generate-estimate
Generates a preliminary timeline and budget estimate for an IT project (Phase 1 — Initiation). Reads available project files (client questionnaire, project charter, constraints, team list), applies analogy-based estimation using built-in agent knowledge of typical IT projects, and produces a three-scenario (optimistic…
generate-questionnaire
A questionnaire builder for IT projects. It creates either a client questionnaire for gathering requirements at the start or a lessons-learned questionnaire for the team at the end, and can organize the answers.