Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/etrebels/claude-code-growth-osnpx agentmods add commands/etrebels/claude-code-growth-os/midday-checkinWrote 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/commands/etrebels/claude-code-growth-os/midday-checkin)<a href="https://agentmods.dev/commands/etrebels/claude-code-growth-os/midday-checkin"><img src="https://agentmods.dev/badge/commands/etrebels/claude-code-growth-os/midday-checkin/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/commands/etrebels/claude-code-growth-os/midday-checkin"><img src="https://agentmods.dev/badge/commands/etrebels/claude-code-growth-os/midday-checkin.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.00016 | $0.00463 |
| Opus 5.5 | $0.00006 | $0.00185 |
| Sonnet 5.5 | $0.00003 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
midday-checkin 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 1mo 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.
What it actually says
Midday Check-in
Generic chassis variant. If a private operating repo (e.g. your own growth-os) defines a command with this name, that version is canonical for that repo's data.
A quick reset. In order:
- Read
ops/priorities.mdand today's top three (from this morning's/morning-briefing, or the latestops/daily-log.mdentry). - Mark what's done. Flag anything at risk of not happening today.
- Name the one thing that must happen this afternoon — and protect time for it. (It can be a deal or a post-sale move — whichever is most at risk of slipping.)
Keep it to a few lines. No recap of things already finished. If a deal moved this morning, persist the stage/score change per .claude/rules/crm-usage.md — safe writes only.
Depth
- quick: the one thing that must happen this afternoon.
- standard: the full reset above.
- deep: re-rank the afternoon against the week's priorities, not just today's.
Closing step — record the run (never skip)
A run that died and a run with nothing to say must not look alike. Finish by writing the outcome to disk, from the repo root:
bash .claude/scripts/routine-state.sh ok midday-checkin "<what landed — one short line>"
That writes ops/runs/midday-checkin.last, clears any FAILED- marker, and returns an OK line. Print that line last, so the run output ends with proof it finished.
If the ritual could not complete — a source unreachable, a write that would not land, a step that needs you — record that instead, and say what blocked it:
bash .claude/scripts/routine-state.sh fail midday-checkin "<what blocked it>"
The FAILED- marker stays on disk until the next good run of this ritual, and every session start reads it. Recording a failure is this ritual finishing correctly; leaving nothing behind is the failure.
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.
- 1mo ago Changed · +18 lines f28392c34b78
- 1mo ago First seen · 21 lines · 16 tokens per session scan A 01a11cd366c2
midday-checkin is a command published in the GitHub repository etrebels/claude-code-growth-os (21 stars, last pushed 7d ago), licensed MIT. It adds 16 tokens to every session and 463 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-08-30.
Other commands, from other repositories
slack-comms
Read, write, and manage Slack communications. Supports reading channel history, posting messages, summarizing threads, replying in threads, and posting structured action notifications.
comms-scan
Unified communication triage across email, social mentions, and project management in one pass.
monday
Monday morning startup sequence. Runs multiple commands in order with approval checkpoints, then opens the weekly dashboard.
audit-release
Diagnose release-readiness against the Starter Series quality bar — matched starter, version-vs-last-tag drift, CHANGELOG drift vs merged PRs, and publish-workflow kind. Read-only.
sugar-review
Review and manage pending Sugar tasks interactively.
go-to-market
Build a complete go-to-market strategy based on the requirements found in files.requirements.