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 adamjali/claude-skills --skill explaingit clone --depth 1 https://github.com/adamjali/claude-skillsWrote 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/adamjali/claude-skills/explain)<a href="https://agentmods.dev/skills/adamjali/claude-skills/explain"><img src="https://agentmods.dev/badge/skills/adamjali/claude-skills/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/skills/adamjali/claude-skills/explain"><img src="https://agentmods.dev/badge/skills/adamjali/claude-skills/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.00162 | $0.03746 |
| Opus 5 | $0.00081 | $0.01873 |
| Sonnet 5 | $0.00032 | $0.00749 |
| Haiku 4.5 | $0.00016 | $0.00375 |
Grade C, and why
explain scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
If yes: `rm -rf $REPO_DIR` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **B6 Namespace** (if "any others?"): DNS+curl+search candidate domains, classify, find operator clusters, flag defensive-buy domains, teardown only the genuinely-distinct YES set. How it starts
The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<essential_principles>
How This Skill Works
Two modes, auto-routed by subject (see routing table):
- Mode A — Repo / concept / docs (the cheap path): research → clone (if repo) → explore → synthesize → output. Loose parallel agents are fine.
- Mode B — Live web product / competitor / data product / algorithm / landscape (the full shebang): scout → confirm → Workflow-orchestrated deep recon → real-browser capture → reverse-engineer-to-validated-code → synthesize. Read
@references/competitor-teardown.mdand follow it.
Subject-type routing
| Subject | Signal | Mode | Spine |
|---|---|---|---|
| GitHub repo | github.com |
A | clone + Explore agents |
| Concept / tech | no URL | A | researcher agents |
| Docs / static site | URL, informational | A | researcher + WebFetch |
| Live product / app / SaaS / competitor | URL is a product; "competitor/teardown/vs us/how do they" | B | browser + Workflow + per-subject schema |
| Calculator / estimator / predictor / pricing / ranking | a formula/algorithm to crack | B | live-probe grid → runnable reference impl → validate |
| Whole landscape | "find all the others / everyone in this space" | B | namespace discovery → teardown the YES set |
Tiebreaker: if a URL is BOTH a product and has docs, default to B — the scout pass is cheap and downgrades to A if there's nothing to tear down.
Execution Rules
- Right tool for scale: Mode A = parallel Task/Agent calls. Mode B = the Workflow tool (pipelines, structured-output schemas, resume) once there are 3+ subjects or multi-phase work.
- Ground, then confirm: Mode B does a cheap scout pass + a confirm gate (scope + recon boundary + browser) before the expensive dive — unless the user already said "full shebang / go deep / everything."
- Reverse-engineer to runnable, validated code for any calculator/algorithm; benchmark vs the authoritative ground truth, not the competitor's own claim.
- Visual-heavy: every major concept gets a diagram or table.
- Dual output: display the exec read + file index in conversation; save the full doc set to
~/.claude/explanations/<date>_<slug>/. - Resilient: heavy Mode-B research runs as a background Workflow; persist artifacts incrementally; resume (
resumeFromRunId) on a cutoff. - Clean up: offer to delete cloned repos / saved files when done. </essential_principles>
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 308 lines · 162 tokens per session scan C 58c1619cf5df
explain is a skill published in the GitHub repository adamjali/claude-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 162 tokens to every session and 3,746 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
analyze
Reads input artifact(s) — codebase, planning session, refactor plan, or generic doc — and writes a tour-spec.json describing sections, embedded sources, cross-refs, quizzes, and external link maps. Use when the user wants a fresh learning guide built from source material; auto-hands-off to learning-guide:render.…
branch-recap
Takes stock of what a branch actually changed, before it gets pushed — works out the scope itself, then lays the change out group by group in one pass: files touched, what was done and why, how, and what deserves a second look, quoting code only where a remark needs it rather than reprinting the diffs. Closes on a…
audit-context
Measures where a project's Claude context is going before applying any of clean-context's levers. Reports what Glob discovers with and without ignore files applied, the twenty largest files in the repo and which are generated, the cumulative size of every CLAUDE.md loaded for this working directory, and how many MCP…
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read: filtered to what they would actually notice, one bullet per idea, plain language, no code vocabulary. Works out the scope itself across however many repositories sit in the working directory (a project can span several…
ignore-setup
Set up a project so Claude stops discovering lockfiles, generated code, minified assets and binaries on every search — a managed .ignore, the Glob setting that makes Glob obey it, and a short read-deny list for secrets. Use when someone asks for a .claudeignore, asks to exclude files from the context, says Claude…
plugin-commands
Commands for validating, testing, iterating on, and releasing plugins in this marketplace (claude-toolbelt) — plugin validate, watcher-parity check, eval, --plugin-dir dev loop, plugin tag. Use when validating a plugin before pushing, running skill evals, developing a plugin without touching the installed cache, or…