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 melodic-software/claude-code-plugins --skill morning-briefgit clone --depth 1 https://github.com/melodic-software/claude-code-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/melodic-software/claude-code-plugins/morning-brief)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/morning-brief"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/morning-brief/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/melodic-software/claude-code-plugins/morning-brief"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/morning-brief.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.00122 | $0.04506 |
| Opus 5.5 | $0.00049 | $0.01802 |
| Sonnet 5.5 | $0.00024 | $0.00901 |
| Haiku 4.5 | $0.00012 | $0.00451 |
Grade A, and why
morning-brief 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 yesterday.
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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments. [--repo owner/name] [--telemetry-issue N] [--queue-labels A,B,C] [--stale-hours N] [--pr-limit N]. Full form: [--repo owner/name] [--telemetry-issue N] [--queue-labels A,B,C] [--decision-label L] [--stale-hours N] [--stranded-days N] [--pr-limit N] [--lane-workflows A,B] [--lane-read-limit N] [--max-turns-hits N]. Read-only on GitHub; omit to view the current repo
Pre-computed context
Repo: !gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || git remote get-url origin 2>/dev/null | sed -E 's#\.git$##; s#.*github\.com[:/]##' | grep -E '^[^/]+/[^/]+$' || echo "unknown (run inside a checkout with a GitHub origin remote, or pass --repo)"
gh: !command -v gh >/dev/null 2>&1 && echo "present" || echo "MISSING (required)"
jq: !command -v jq >/dev/null 2>&1 && echo "present" || echo "MISSING (required)"
Variables
Arguments: $ARGUMENTS
Purpose
The 30-60 minute operator morning pass begins with the same hand-run gh queries
every day. This skill collapses them into a single 5-second picture for the current
repo, so the pass starts from a complete view instead of ad-hoc lookups.
Read-only and gh-based. It runs only gh read queries and never mutates
labels, comments, issues, or PRs. Its one local write is the stranded-findings
bookmark under the plugin data dir. Owner/repo is derived from gh repo view, or
from the checkout's origin remote when that call is unavailable (never
hardcoded), so it is reusable across repos.
Run it
"${CLAUDE_SKILL_DIR}/scripts/morning-brief.sh" --data-dir "${CLAUDE_PLUGIN_DATA}" $ARGUMENTS
Print the script's output verbatim; do not re-query the sections by hand.
Pass the data dir on the command line: the script cannot read it from its environment under the Bash tool.
- Pointer: https://code.claude.com/docs/en/plugins/manifest-reference#where-each-variable-resolves
- As of: 2026-10-11
- Recheck trigger: that section starts exporting the plugin path variables to commands run through the Bash tool.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +37 lines e55620233314
- 2d ago Changed · +26 lines · +43 tokens per session 5d748bb3dcf7
- 5d ago Changed · -5 lines · -19 tokens per session 33a9d8c00a70
- 8d ago Changed · +20 lines bf23aa5b929e
- 16d ago Changed · +28 lines 15e897ac8e4a
- 17d ago Changed 0f68aef47aac
- 20d ago Changed · +2 lines 0c5e7d874ce3
- 21d ago Changed · -29 tokens per session e35a1839cb0c
- 1mo ago Changed · +51 lines cd2a8df6fb4a
- 1mo ago First seen · 84 lines · 127 tokens per session scan A 050112c4ff5e
morning-brief is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 122 tokens to every session and 4,506 once invoked, about $0.0005 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 skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
team-workspace
Set up or work with a git-backed team workspace for co-owned artifacts — charters, strategy docs, decision records — separate from private reflections. Triggers: "share our team charter with the team", "set up a shared haku workspace", "put our strategy doc in the team repo", "how do teams use haku together".…
git-jira-integration
Integration between Git workflows and Jira issues. Generates branch names from issues, validates commit messages, and provides PR context from Jira specifications.
teamboard
Shared team board: claim a work item before starting, hand it over, finish it. The claim is a git-ref lock, so two people cannot take the same item.
commitments
Use to track promises in /haku-work-reflections/commitments.md and keep them from going stale. Trigger phrases include "what have I committed to", "add a commitment", "I promised X by Friday", "am I overcommitted", "help me say no to this", "I need to renegotiate a deadline". Renegotiate early; pressure-test new asks.…