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 agentmods add commands/fergupa/claude_plugins/digestgit clone --depth 1 https://github.com/fergupa/claude_pluginsWhat 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 | $0.00012 | $0.01250 |
| Opus 5 | $0.00006 | $0.00625 |
| Sonnet 5 | $0.00002 | $0.00250 |
| Haiku 4.5 | $0.00001 | $0.00125 |
Grade A, and why
digest 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 2d 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.
This is a copy
100% identical to digest — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Digest Command
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Scan recent activity across all connected sources and generate a structured digest highlighting what matters.
Instructions
1. Parse Flags
Determine the time window from the user's input:
--daily— Last 24 hours (default if no flag specified)--weekly— Last 7 days
The user may also specify a custom range:
--since yesterday--since Monday--since 2025-01-20
2. Check Available Sources
Identify which MCP sources are connected (same approach as the search command):
- ~~chat — channels, DMs, mentions
- ~~email — inbox, sent, threads
- ~~cloud storage — recently modified docs shared with user
- ~~project tracker — tasks assigned, completed, commented on
- ~~CRM — opportunity updates, account activity
- ~~knowledge base — recently updated wiki pages
If no sources are connected, guide the user:
To generate a digest, you'll need at least one source connected.
Check your MCP settings to add ~~chat, ~~email, ~~cloud storage, or other tools.
3. Gather Activity from Each Source
~~chat:
- Search for messages mentioning the user (
to:me) - Check channels the user is in for recent activity
- Look for threads the user participated in
- Identify new messages in key channels
~~email:
- Search recent inbox messages
- Identify threads with new replies
- Flag emails with action items or questions directed at the user
~~cloud storage:
- Find documents recently modified or shared with the user
- Note new comments on docs the user owns or collaborates on
~~project tracker:
- Tasks assigned to the user (new or updated)
- Tasks completed by others that the user follows
- Comments on tasks the user is involved with
~~CRM:
- Opportunity stage changes
- New activities logged on accounts the user owns
- Updated contacts or accounts
~~knowledge base:
- Recently updated documents in relevant collections
- New documents created in watched areas
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.
- 2d ago First seen · 173 lines · 12 tokens per session scan A 124762e648ad
digest is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,250 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to digest, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.