digest

digest is a command for Claude Code from kyopark2014/agent-plugins. It costs 12 tokens per session (1,250 once invoked), scanned A, original, MIT.

A command that collects recent activity from connected services such as chat, email, cloud storage, project trackers, CRM systems, and knowledge bases, then creates a daily or weekly summary.

In plain words
What is it for?
Reviewing the last day or week of activity, or creating a summary for a custom date range.
Why use it?
It removes the need to check each connected service separately for important updates.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md)..

Good fit Reviewing the last day or week of activity, or creating a summary for a custom date range.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/kyopark2014/agent-plugins
agentmods
npx agentmods add commands/kyopark2014/agent-plugins/digest

Made for: Claude Code.

Wrote 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.

agentmods badge for digest

README.md
[![agentmods](https://agentmods.dev/badge/commands/kyopark2014/agent-plugins/digest/github.svg)](https://agentmods.dev/commands/kyopark2014/agent-plugins/digest)
Your own site
<a href="https://agentmods.dev/commands/kyopark2014/agent-plugins/digest"><img src="https://agentmods.dev/badge/commands/kyopark2014/agent-plugins/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.

agentmods 80×15 button for digest

Your own site · 80×15
<a href="https://agentmods.dev/commands/kyopark2014/agent-plugins/digest"><img src="https://agentmods.dev/badge/commands/kyopark2014/agent-plugins/digest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,250 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.01250
Opus 5.5 $0.00005 $0.00500
Sonnet 5.5 $0.00002 $0.00250
Haiku 4.5 $0.00001 $0.00125

Measured 1mo ago against content hash 124762e648ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • digest — 100% identical, 0 lines differ
application/plugins/enterprise-search/commands/digest.md · 173 lines

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

Read the full file on GitHub · 173 lines

Changes

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.

  1. 1mo ago First seen · 173 lines · 12 tokens per session scan A 124762e648ad

Subscribe to this mod's changes

digest is a command published in the GitHub repository kyopark2014/agent-plugins (4 stars, last pushed 8d ago), licensed MIT. It adds 12 tokens to every session and 1,250 once invoked, about $0.0000 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-31.