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.
git clone --depth 1 https://github.com/etrebels/claude-code-growth-osWrote 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/morning-briefing)<a href="https://agentmods.dev/commands/etrebels/claude-code-growth-os/morning-briefing"><img src="https://agentmods.dev/badge/commands/etrebels/claude-code-growth-os/morning-briefing/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/morning-briefing"><img src="https://agentmods.dev/badge/commands/etrebels/claude-code-growth-os/morning-briefing.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.00012 | $0.00612 |
| Opus 5 | $0.00006 | $0.00306 |
| Sonnet 5 | $0.00002 | $0.00122 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
morning-briefing 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Morning Briefing
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.
Run my morning ritual, in order:
-
Priorities. Read
ops/priorities.mdand list what's still open. -
Yesterday. Read the most recent entry in
ops/daily-log.md. Summarize what got done and what's still hanging. -
Pipeline. Read the open pipeline —
ops/pipeline.md, or a connected CRM per.claude/rules/crm-usage.md(read-only this run). Flag stalls (no activity in 7+ days), deals closing soon, and qualification red flags. Top-tier first. -
Field intel → marketing. Scan the latest
ops/daily-log.mdentry (and any fresh meeting notes) for recurring objections, competitor mentions, missing proof, or win/loss reasons, and surface them asMARKETING-ACTIONlines inops/feedback-log.md— the one home for tagged loop lines — so marketing can act. This is what themarketing-feedbackskill does. Skip if there's nothing new. -
Post-sale read. Scan
ops/customers.mdfor anything that needs attention today: renewals inside 60 days, accounts at 🔴/🟡 (usage down, champion quiet, single-threaded), and adoption stalls (a workflow never turned on). Then surface the top one or two open items inops/roadmap-signals.md. Skip a line if the file is empty. -
Inbox + calendar. If a mail MCP and calendar MCP are connected, run
inbox-digestandcalendar-followup— unread newsletter digest and any meetings older than 3 days with no follow-up. Skip either step if the MCP isn't wired. -
Today's top three. First ask the forward question — what is the single highest forward-moving action today? — then propose exactly three priorities, each with a one-line reason. At least one must be that forward-moving action, not just maintenance; lean toward covering both sides of the bowtie when both have live work.
-
Offer. Ask if I want to append today's plan to
ops/daily-log.md.
Keep it short. Lead with the top three. No preamble. Render the to-do list the one canonical way — see .claude/rules/todo-single-source.md — and compose the briefing around it; don't re-group it here.
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.
- 9d ago First seen · 27 lines · 12 tokens per session scan A 489e3ebd58e2
morning-briefing is a command published in the GitHub repository etrebels/claude-code-growth-os (20 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 612 once invoked, about $0.0001 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-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.
go-to-market
Build a complete go-to-market strategy based on the requirements found in files.requirements.
learn
Run /summary internally, then audit what scripts, skills, commands, or memories need updating based on this session's work.