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/demo-briefing)<a href="https://agentmods.dev/commands/etrebels/claude-code-growth-os/demo-briefing"><img src="https://agentmods.dev/badge/commands/etrebels/claude-code-growth-os/demo-briefing.svg" alt="Measured on agentmods" 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.00028 | $0.00384 |
| Opus 5 | $0.00014 | $0.00192 |
| Sonnet 5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
demo-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 8d 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
Demo 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 the morning ritual against the fictional sample data in demo/. Nothing here is real — these are made-up companies.
In order:
- Priorities. Read
demo/priorities.mdand list what's open. - Pipeline. Read
demo/pipeline.md. Flag any deal with no activity in 7+ days or no next step — call out the top-tier ones first. - Commitments → tasks. Read every note in
demo/meetings/. Pull out each commitment "you" made and turn it into a task with an owner and a due date. - Field intel → marketing. Read
demo/feedback-log.mdand surface theMARKETING-ACTIONlines — the recurring objections and missing proof points sales should hand to marketing. This is the sales→marketing loop. - Retention signal → product. From the same
demo/feedback-log.md, surface theRETENTION-RISK(andEXPANSION-SIGNAL) lines — accounts in onboarding or production whose adoption is slipping or who are ready to grow, routed to product/CS. This is the post-sale→product loop — the half most teams never wire. - Today's top three. Propose exactly three priorities for today, each with a one-line reason. At least one must advance a deal; at least one must protect or expand an existing customer.
Keep it tight. Lead with the top three. No preamble.
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.
- 8d ago First seen · 21 lines · 28 tokens per session scan A cc65e5977a25
demo-briefing is a command published in the GitHub repository etrebels/claude-code-growth-os (20 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 384 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.