digest

digest is a command for Claude Code from avelikiy/great_cto. It costs 33 tokens per session (1,119 once invoked), scanned A, original, MIT.

A weekly engineering report that summarizes delivery speed, incidents, technical debt, architecture decisions, and unresolved work.

In plain words
What is it for?
Use it to prepare a regular CTO update or a board-focused report covering engineering health and recommendations.
Why use it?
It brings scattered engineering signals into one short update so leaders can see trends and decide what needs attention.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; positional $N argument.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the great-cto plugin — 40 skills, 44 commands, 70 agents shipped together

Good fit Use it to prepare a regular CTO update or a board-focused report covering engineering health and recommendations.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add avelikiy/great_cto
Claude Code
/plugin install great-cto

Made for: Claude Code.

Or install great-cto, the plugin that ships this one along with the rest of its 40 skills, 44 commands, 70 agents.

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/avelikiy/great_cto/digest.svg)](https://agentmods.dev/commands/avelikiy/great_cto/digest)
Your own site
<a href="https://agentmods.dev/commands/avelikiy/great_cto/digest"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/digest.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 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,119 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.00033 $0.01119
Opus 5 $0.00016 $0.00560
Sonnet 5 $0.00007 $0.00224
Haiku 4.5 $0.00003 $0.00112

Measured today against content hash b98a82f17499, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 today.

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.

commands/digest.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the great_cto Digest command. Produce a weekly engineering digest for the CTO. Keep the response under 60 lines.

Step 1 — Run helper, write to file (no inline expansion)

ARGS="${ARGUMENTS:-}"
DAYS=7; BOARD=0
for arg in $ARGS; do
  case "$arg" in
    board) BOARD=1 ;;
    [0-9]*) DAYS="$arg" ;;
    Q[1-4]) DAYS=90 ;;
  esac
done

PLUGIN_DIR=${CLAUDE_PLUGIN_ROOT:-$(ls -d ~/.claude/plugins/cache/*/great_cto/*/ 2>/dev/null | sort -V | tail -1 | sed 's|/$||')}
HELPER="${PLUGIN_DIR}/scripts/cmd-data/digest-data.sh"
[ -f "$HELPER" ] || HELPER="$(pwd)/scripts/cmd-data/digest-data.sh"

OUT_DIR=".great_cto/cache"; mkdir -p "$OUT_DIR"
OUT="${OUT_DIR}/digest-out.txt"
DAYS="$DAYS" bash "$HELPER" > "$OUT" 2>&1
SIZE=$(wc -c < "$OUT" 2>/dev/null || echo 0)
LINES=$(wc -l < "$OUT" 2>/dev/null || echo 0)
echo "DIGEST_READY days=$DAYS board=$BOARD out=$OUT size=${SIZE}B lines=${LINES}"

Don't pipe helper output to stdout — that re-expands it into your prompt and risks Prompt is too long in heavy-context sessions.

Step 2 — Read the file

Use the Read tool on the path printed as out=. Default to reading the first 300 lines; only read more if the helper truncated. Sections emitted (only when relevant): ## DORA, ## RELIABILITY, ## DELIVERY, ## TEAM, ## COST, ## OPS, ## AGENTS.

Step 3 — Render

If BOARD=0 (default), format as engineering digest:

# Weekly digest · last <DAYS>d · <YYYY-MM-DD>

## Delivery
- <N> features shipped (<delta vs prior week>)
- <N> hotfixes · <N> rework

## Reliability
- DORA: deploys/wk <X> · lead-time <X>h · MTTR <X>m · CFR <X>%
- SLO burn: <service> <Xx> over budget on <metric>
- p95 latency: <X>ms (<delta>)

## Cost
- $<X>/day avg · projected month $<X> (<X>% of $<budget> budget)
- Top mover: <agent> +<X>% MoM

## Team & ops
- On-call: <name> (<days remaining>)
- Open RFCs: <N> (<oldest age>)
- Ownership gaps: <N> services without owner

## Insights
- <2-3 derived observations — patterns, anomalies, things worth attention>

→ Run /burn for SLO drill-down, /cost for capacity, /inbox for action items.

Read the full file on GitHub · 114 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. today Changed b98a82f17499
  2. 2d ago Changed 8227d985b7c1
  3. 4d ago First seen · 114 lines · 33 tokens per session scan A b4c898b8d45a

Subscribe to this mod's changes

digest is a command published in the GitHub repository avelikiy/great_cto (89 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,119 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-09-03.