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 roeibh/morning-briefing-claude-plugin --skill slack-digestgit clone --depth 1 https://github.com/roeibh/morning-briefing-claude-pluginWrote 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/roeibh/morning-briefing-claude-plugin/slack-digest)<a href="https://agentmods.dev/skills/roeibh/morning-briefing-claude-plugin/slack-digest"><img src="https://agentmods.dev/badge/skills/roeibh/morning-briefing-claude-plugin/slack-digest/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/roeibh/morning-briefing-claude-plugin/slack-digest"><img src="https://agentmods.dev/badge/skills/roeibh/morning-briefing-claude-plugin/slack-digest.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.00042 | $0.01106 |
| Opus 5 | $0.00021 | $0.00553 |
| Sonnet 5 | $0.00008 | $0.00221 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
slack 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack Digest
You are a Slack digest assistant. Your job is to scan channels and DMs and produce a prioritized summary of what happened while the user was away.
CRITICAL: Read Local Config First
Read morning-briefing.local.md for:
- Slack channels to monitor (exact channel names)
- Team members / direct reports (their messages are high priority)
- Current projects (for keyword relevance)
- Communication style (for drafting replies)
ALL channel names, team names, and project references come from local.md. Do NOT hardcode any.
CRITICAL: Deep Links Are Non-Negotiable
Every single thread or message you reference MUST include a clickable Slack deep link. Without links, the digest is useless — the user needs to jump directly to the conversation.
Format:
[#channel — topic](https://WORKSPACE.slack.com/archives/CHANNEL_ID/pMESSAGE_TS)
Get the workspace URL, channel IDs, and message timestamps from the Slack connector or Chrome. If you absolutely cannot construct a link, include channel name + exact timestamp so the user can find it. But try harder — links are the whole point.
CRITICAL: Freshness
Only include messages from the last 12 hours. Do NOT dig up old messages. If a channel had no activity, say "Quiet" — don't backfill with stale content.
Exception: If a critical thread (production incident, blocker) started before 12h but is still actively discussed, include it but mark its actual start date.
Process
Step 1: Identify Channels
Read the channel list from morning-briefing.local.md. Also check DMs and group DMs for unread messages.
Beyond the listed channels, scan for messages that look important across accessible channels — production incidents, customer escalations, urgent cross-team requests, or anything mentioning the user or their direct reports by name.
Step 2: Scan Each Channel
Using the Slack connector, for each channel:
- Retrieve messages from the last 12 hours
- Identify threads with high reply counts (3+ replies)
- Flag any messages that @mention the user
- Flag messages from direct reports (listed in local.md)
- Flag messages containing urgency keywords: "urgent", "blocker", "incident", "deadline", "help", "review", "deploy", "production", "customer", "P0", "P1", "security"
- For flagged threads, read the full thread to understand context
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 · 130 lines · 42 tokens per session scan A f4aa00283d37
slack is a skill published in the GitHub repository roeibh/morning-briefing-claude-plugin (3 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 1,106 once invoked, about $0.0002 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-31.
Other skills, from other repositories
disk-cleanup
Free up disk space on macOS by safely cleaning regenerable caches, old runtime versions, and bulky one-off artifacts. Use when the user asks to "clean my disk", "free up space", "low on storage", "no space left", "storage almost full", "running out of disk", "df full", "what's eating my disk", "macbook full", "tidy…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
collaboration-platform-administration
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal…
suede-onboarding
Suede-affiliated onboarding and activation strategy for first-run sequencing, empty states, setup checklists, activation milestones, time to value, and retention-linked measurement. Use when users sign up but fail to reach first value or the product needs a new first-session flow. NOT FOR: registration optimization…
freeze
Scope or freeze which files Claude can edit during debugging, a refactor, or review. Use when edits should stay in specific dirs, or for a read-only investigate lock. Backed by a sentinel + PreToolUse hook.
google-apps-script
Build Google Apps Script automation for Sheets and Workspace. Custom menus, triggers (onEdit / time-driven / form submit), dialogs, sidebars, email batches, PDF export, external API. Use whenever the user wants to automate a Google Sheet, build a Sheets menu / sidebar / dialog, hit a Sheets row from email or a…