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 GPT-AGI/Clawd-Code --skill explain-codegit clone --depth 1 https://github.com/GPT-AGI/Clawd-CodeWrote 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/gpt-agi/clawd-code/explain-code)<a href="https://agentmods.dev/skills/gpt-agi/clawd-code/explain-code"><img src="https://agentmods.dev/badge/skills/gpt-agi/clawd-code/explain-code/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/gpt-agi/clawd-code/explain-code"><img src="https://agentmods.dev/badge/skills/gpt-agi/clawd-code/explain-code.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.00038 | $0.00134 |
| Opus 5.5 | $0.00015 | $0.00054 |
| Sonnet 5.5 | $0.00008 | $0.00027 |
| Haiku 4.5 | $0.00004 | $0.00013 |
Grade A, and why
explain-code 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- explain-code — 100% identical, 25 lines differ
- explaining-code — 95% identical, 2 lines differ
- explaining-code — 95% identical, 2 lines differ
- explaining-code — 95% identical, 2 lines differ
- explaining-code — 95% identical, 2 lines differ
- explain-code — 89% identical, 2 lines differ
What it actually says
When explaining code, always include:
- Start with an analogy: Compare the code to something from everyday life
- Draw a diagram: Use ASCII art to show the flow, structure, or relationships
- Walk through the code: Explain step-by-step what happens
- Highlight a gotcha: What's a common mistake or misconception?
Keep explanations conversational. For complex concepts, use multiple analogies.
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 · 14 lines · 38 tokens per session scan A aa12f1242377
explain-code is a skill published in the GitHub repository GPT-AGI/Clawd-Code (705 stars, last pushed 26d ago), licensed MIT. It adds 38 tokens to every session and 134 once invoked, about $0.0002 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-30.
Other skills, from other repositories
blog-post
Writes and structures long-form blog posts, creates tutorial outlines, and optimizes content for SEO with cover image generation. Use when the user asks to write a blog post, article, how-to guide, tutorial, technical writeup, thought leadership piece, or long-form content.
playwright
Use when the task requires capturing or automating a real browser from the terminal.
live-tutorial
Create an annotated MP4 tutorial from a workflow demonstrated in the owner's actual application. Use when asked for a tutorial video, not merely to watch an action live.
flashcards
Create strict JSON flashcard decks for active-recall study.
quiz
Create strict JSON single-answer multiple-choice quizzes.
good-docs-writing
Writing style guide derived from Modal's documentation voice. Apply when writing or editing docs, guides, tutorials, or technical prose that should read direct, second-person, confident, low-jargon, and example-first. Use to draft new docs in this voice or to revise existing prose toward it.