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/coralogix/canopyWrote 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/coralogix/canopy/morning-briefing)<a href="https://agentmods.dev/commands/coralogix/canopy/morning-briefing"><img src="https://agentmods.dev/badge/commands/coralogix/canopy/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/coralogix/canopy/morning-briefing"><img src="https://agentmods.dev/badge/commands/coralogix/canopy/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.00000 | $0.00397 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 11d 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
/morning-briefing
Prepare a morning work briefing: what happened yesterday, what to focus on today.
Steps
- Load context from memory. Read what projects and teams the developer is tracking.
- Check yesterday's activity (use whichever tools are available):
- Git:
git log --since="yesterday" --until="now" --oneline --author="$(git config user.email)"across known repos - GitHub MCP (if configured): recent commits, merged PRs, comments
- If nothing is available, ask: "What did you work on yesterday?"
- Git:
- Check today's priorities (use whichever tools are available):
- GitHub MCP: open PRs needing review, assigned open issues, issues with upcoming deadlines
- If not available, use memory of known priorities
- Flag anything that needs attention:
- PRs that have been open > 3 days
- Blocked items from memory
- Anything the developer flagged as urgent in a previous session
- Format the briefing (see output format below).
Output Format
Good morning [name if known]!
**Yesterday**
- [most important thing completed]
- [other notable activity]
**Today**
- [top priority]
- [second priority]
- [anything else]
**Watch out for**
- [PR/issue/thing that needs attention today]
Rules
- Keep each bullet to one line
- Skip sections that have nothing meaningful (don't write "Yesterday: nothing" — just omit it)
- If you're working from memory only (no git/GitHub access), say so briefly at the end: (based on memory — connect GitHub for live data)
- Don't repeat the same priorities every day — if something has been in "Today" for 3 sessions without progress, flag it as potentially blocked
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.
- 11d ago First seen · 45 lines · 0 tokens per session scan A 9a295853fd5e
morning-briefing is a command published in the GitHub repository coralogix/canopy (89 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 397 tokens. 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
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.