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 juxt/claude-plugins --skill explicategit clone --depth 1 https://github.com/juxt/claude-pluginsWrote 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/juxt/claude-plugins/explicate)<a href="https://agentmods.dev/skills/juxt/claude-plugins/explicate"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/explicate/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/juxt/claude-plugins/explicate"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/explicate.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.00074 | $0.01541 |
| Opus 5.5 | $0.00030 | $0.00616 |
| Sonnet 5.5 | $0.00015 | $0.00308 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
explicate 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 8d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chalk Explicate — Unfolding an Area of the Code
Interpret MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, etc. per RFC 2119.
To explicate is to unfold: to make explicit what is implicit. An area's decisions and their consequences are folded into its code; the record — commits, PRs, issues — holds some of the why, and the rest has to be inferred. The reader is an engineer who has lost touch with the area, or never had it, and whose attention is the scarce resource.
Success: the user holds a working model of the area as it stands, knows which decisions shaped it and what they cost elsewhere, and can tell which of that is on the record and which is inferred.
$ARGUMENTS names the area, and may carry a focus or a since-point.
A since-point is a commit, tag or date; anything else is a focus.
Before you start
- Load
chalk:voice. Its register applies; its palette doesn't. An explication is a terminal reply, not a GitHub artefact.
1. Bound the area
A path or namespace is the area as given.
A concept — "how does our disk caching work" — MUST be located and its boundary confirmed before it's explicated. Find its entry points, the namespaces and classes that implement it, and where it meets the rest of the system; propose that boundary, and wait. An explication of the wrong boundary spends the attention it exists to save.
2. Ground it in the code and the record
The code says how the area works now; the record says why.
-
Now is the checkout's HEAD, and the overview names it.
-
Read the record back from the code:
git logand blame over the area → the commits → the PRs that landed them → the issues those PRs name. -
Read what's in flight: open PRs and issues touching the area.
-
The since-point is the one in the arguments, else the user's own last commit in the area, else none. A user new to the area gets no account of what's changed.
-
You MAY fan out read-only sub-agents — history, structure, dependents — and combine their findings here. The combining stays in this context, where the follow-ups are answered.
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.
- 8d ago First seen · 129 lines · 74 tokens per session scan A 584e80a90950
explicate is a skill published in the GitHub repository juxt/claude-plugins (10 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 1,541 once invoked, about $0.0003 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-10-09.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…