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-copilot-cowork-plugins --skill operating-rhythmgit clone --depth 1 https://github.com/alexclowe/awesome-copilot-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-copilot-cowork-plugins/operating-rhythm)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/operating-rhythm"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-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-copilot-cowork-plugins/operating-rhythm"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-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.
This is a copy
100% identical to operating-rhythm — 0 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.
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-copilot-cowork-plugins (21 stars, last pushed 5d 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. It is 100% identical to operating-rhythm, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
calle
Use CALL-E from Codex through the calle CLI. Use for CALL-E setup checks, authentication recovery, phone call planning, planned call execution, and call status checks.
dmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
codex-skin-pack-installer
Install Codex themes and Codex skin packs with npx skills. Use this skill when a user wants Codex to find, download, validate, apply, switch, remix, or restore Codex desktop themes such as caishen-readable, caishen-lite, mythic-guardian-noir, global-founder-bright, export-night, or caishen-max. It stages verified…
cost-aware-llm-pipeline
A planning guide for choosing language models and managing the amount of conversation context used by an AI coding workflow. It groups tasks by complexity and gives rules for avoiding context overflow during long sessions.
clueless
A mode that changes how an agent handles tasks when the user cannot review the result in that area. It makes the agent act as the expert, reviewer, and person responsible for identifying decisions the user may not understand.
clueless-help
Use when the user asks how clueless works, what its commands or levels are, or types /clueless-help.