Borrowing it
Nothing to install: this file belongs to crbnos/carbon. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/crbnos/carbon/main/.claude/skills/explain/SKILL.mdgit clone --depth 1 https://github.com/crbnos/carbonWrote 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/crbnos/carbon/explain)<a href="https://agentmods.dev/skills/crbnos/carbon/explain"><img src="https://agentmods.dev/badge/skills/crbnos/carbon/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/crbnos/carbon/explain"><img src="https://agentmods.dev/badge/skills/crbnos/carbon/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.03761 |
| Opus 5.5 | $0.00065 | $0.01504 |
| Sonnet 5.5 | $0.00032 | $0.00752 |
| Haiku 4.5 | $0.00016 | $0.00376 |
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 26d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 26d ago First seen · 276 lines · 162 tokens per session scan A 6cc41f41a76c
explain is a skill published in the GitHub repository crbnos/carbon (2,783 stars, last pushed today), with no licence file. It adds 162 tokens to every session and 3,761 once invoked, about $0.0006 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-04.
Other skills, from other repositories
readme-writing-readme-files
README quality standards for engaging, accessible, scannable content including problem-solution hooks, plain language (no unexplained jargon), acronym context, paragraph limits (≤5 lines), benefits-focused language, visual hierarchy, and progressive disclosure. Essential for creating effective README files that…
docs-validating-software-engineering-separation
Validates software engineering documentation separation between OSE Platform style guides (docs/explanation/) and AyoKoding educational content (apps/ayokoding-www/). Ensures no duplication, proper prerequisite statements, and style guide focus on repository-specific conventions only.
docs-validating-links
Link validation methodology for markdown links including format requirements, path validation, broken link detection, external link verification, and checker implementation patterns.
specs-validating-structure
Validation methodology for specs/ folders — nine categories covering README/feature-file structural completeness, Gherkin format compliance, cross-folder consistency, C4 diagrams, cross-references, spec-to-implementation alignment, tree-shape compliance, and BDD/contracts adoption gaps. Used by specs-checker and…
docs-converting-pdf-to-markdown
PDF-to-Markdown conversion fidelity — the crane CLI, criticality levels, and workflow steps shared by the pdf-to-md maker/checker/fixer family.
specs-scaffolding
Mechanics for specs-maker — the four surface-profile directory trees, README/feature-file/C4-diagram content generation, and the PM-readability/placement/structure conventions every scaffolded file follows.