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.
/plugin marketplace add shdennlin/agent-plugins/plugin install digestWrote 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/commands/shdennlin/agent-plugins/explain)<a href="https://agentmods.dev/commands/shdennlin/agent-plugins/explain"><img src="https://agentmods.dev/badge/commands/shdennlin/agent-plugins/explain/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/commands/shdennlin/agent-plugins/explain"><img src="https://agentmods.dev/badge/commands/shdennlin/agent-plugins/explain.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.00031 | $0.01344 |
| Opus 5.5 | $0.00012 | $0.00538 |
| Sonnet 5.5 | $0.00006 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
explain 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain Command
Turn an investigation into understanding. digest explains what changed (delta); explain explains the current state — what something is, how it works end-to-end, why it was designed this way, or where a bug comes from. Output is a self-contained HTML explainer.
Arguments
Parse the following from $ARGUMENTS:
[path|symbol|question]— What to explain: a file/directory path, a function/class name, or a free-form question. Omit entirely to explain the findings of the current conversation (e.g. right after a debugging session).-f, --for <audience>— Tailor the explainer for an audience (free-form string, same as digest). Default: developer.--helpor-h— Show usage information and exit.
Instructions
Step 1: Parse Arguments
- help: if
--helpor-his present, show usage info below and stop. - audience: if
-for--foris present, the next token is the audience string, verbatim. Default:developer. - target: everything else joined as-is (a question may be multiple words).
Help Output
If --help or -h is present, display this and stop:
Usage: /digest:explain [path|symbol|question] [options]
Explain code state: what it is, how it works, why it's designed this way, where a bug comes from.
Produces a self-contained HTML explainer (inline SVG diagrams, collapsible evidence).
Modes:
(no arguments) Explain the findings of the CURRENT conversation
(run right after an investigation or debugging session)
<path> Explain a file or module: role, flow, design history
<symbol> Explain a function/class: role in the whole flow
"<question>" Answer a free-form question, e.g. "why does retry use jitter?"
Options:
-f, --for <audience> Tailor for an audience (manager, non-technical, "new teammate", ...)
-h, --help Show this help message
Examples:
/digest:explain # after debugging: visualize the finding
/digest:explain src/auth/session.ts # how this file works and why it exists
/digest:explain handleRetry # this function's role in the flow
/digest:explain "why saga pattern here?" # design rationale via git archaeology
/digest:explain src/ -f "new teammate" # onboarding tour
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.
- 1mo ago First seen · 125 lines · 31 tokens per session scan A 18f2c9bb185d
explain is a command published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,344 once invoked, about $0.0001 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.
Other commands, from other repositories
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-0-8
A Japanese-language command that displays the current project setup progress.
setup-m365cli.es
Lesson command — Setup de M365 CLI.
prep-role
Deep prep for a specific role's interview process. The user wants to know what to expect, how to win, and what kills candidates at their level.
setup-vercel.es
Command "setup-vercel.es" from minicoohei/ai-agent-camp, covering configuración de vercel cli, step 0: verificar progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: crear cuenta de vercel.