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 instructions/analyticalmonk/explain-this/claude-mdgit clone --depth 1 https://github.com/analyticalmonk/explain-thisWrote 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/instructions/analyticalmonk/explain-this/claude-md)<a href="https://agentmods.dev/instructions/analyticalmonk/explain-this/claude-md"><img src="https://agentmods.dev/badge/instructions/analyticalmonk/explain-this/claude-md.svg" alt="Measured on agentmods" 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 | $0.01325 | $0.01325 |
| Opus 5 | $0.00662 | $0.00662 |
| Sonnet 5 | $0.00265 | $0.00265 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
explain-this CLAUDE.md 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 4d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this repo is
This is a Claude Code and Codex plugin package with three skills that produce single self-contained interactive HTML explainer pages in the style of distill.pub. The repo root holds .claude-plugin/plugin.json, .claude-plugin/marketplace.json, and .codex-plugin/plugin.json; each skill lives at skills/<name>/SKILL.md plus its references/ (and assets/ for the hub). That layout also satisfies the universal skills/<name>/SKILL.md convention, so the same checkout loads as plain skills in Codex, Cursor, Gemini CLI, OpenClaw, etc., and installs via the skills.sh CLI (npx skills add analyticalmonk/explain-this). Keep the skill folders flat at skills/<name>/ - that flat layout is what the skills.sh CLI walks for discovery. There is no source code to build, no test suite, no lint config.
The output of each skill is a generic standalone HTML file. The skills do not assume any parent project, multi-article index, or shared infrastructure.
The three skills and how they relate
- creating-explainers is the hub. It owns the output format (the HTML template, figure archetypes, voice, color palettes) and the
intake -> outline -> scaffold -> prose -> figures -> fact-check -> polishworkflow. It handles file intake, research intake, and the mix of both. - explaining-codebases extends the hub for code. It adds code intake and code-specific figures, and defers to
creating-explainersfor everything about the output. - fact-checking-explainers is the gate both must pass before delivery. It is discipline-enforcing: no explainer ships with an unverified factual claim.
Skills cross-reference each other by name (fact-checking-explainers), never with @-includes (which force-load files and burn context).
Editing these skills
skills/<name>/SKILL.md- workflow, constraints, when-to-use rules. The frontmatterdescriptionis what triggers the skill, so be precise when editing it. Keep descriptions to when-to-use, not a workflow summary.skills/*/references/*.md- lazy-loaded deep references. The SKILL.md files tell Claude to read these only when relevant, so the skills stay light on context. Keep that property: don't inline reference content into a SKILL.md, and don't cross-link references in ways that force-load extras.skills/creating-explainers/assets/article-template.html- the canonical article skeleton with{{PLACEHOLDERS}}. Structural invariants (DPR-awareinitCanvas(), sidebar TOC scroll-tracking, 1060px and 600px responsive breakpoints) live here. If output articles keep getting a layout invariant wrong, fix the template, not the article..claude-plugin/plugin.json- the plugin manifest. Bumpversionon releases..claude-plugin/marketplace.json- the marketplace entry. Keep itsskillslist anddescriptionin sync with the actual skills and withplugin.json..codex-plugin/plugin.json- the Codex plugin manifest. Keep itsskills,version, description, and interface metadata in sync with the Claude plugin metadata and README.skills/<name>/agents/openai.yaml- Codex UI metadata for each skill. Keep display names, short descriptions, and default prompts aligned with the matchingSKILL.md.
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.
- 4d ago First seen · 49 lines · 1,325 tokens per session scan A 4d624e04d8a6
explain-this CLAUDE.md is an instructions file published in the GitHub repository analyticalmonk/explain-this (19 stars, last pushed 1mo ago), licensed MIT. It adds 1,325 tokens to every session, about $0.0066 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-08-30.
Other instructions, from other repositories
rolecraft AGENTS.md
Instructions for Sri-Ln/rolecraft, covering rolecraft — ai agent instructions, what rolecraft is, voice and tone, sources of truth and data contract (critical).
hplan CLAUDE.md
Instructions for kimsanguine/hplan, covering claude.md — hplan project rules (adk l1: memory), hplan context, 9 behavioral rules, rule 1 — think before coding and rule 2 — simplicity first.
agent-teacher CLAUDE.md
Claude Code instructions for JackyYang258/agent-teacher, covering agentteacher, before you start, common commands and project-specific hard rules.
vibe-engineering AGENTS.md
Instructions for ash1794/vibe-engineering, covering vibe-engineering, skills, invocation, tool mapping and project conventions.
ed3d-plugins CLAUDE.md
Claude Code instructions for ed3dai/ed3d-plugins, covering ed3d-plugins, conventions, task invocations use xml syntax and version updates require marketplace and changelog sync.
forge CLAUDE.md
Instructions for zjio26/forge, covering claude.md, project overview, architecture, wave-based processing and test layering.