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 skills/rmyndharis/antigravity-skills/code-documentation-code-explainnpx skills add rmyndharis/antigravity-skills --skill code-documentation-code-explaingit clone --depth 1 https://github.com/rmyndharis/antigravity-skillsWhat 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.00039 | $0.00347 |
| Opus 5 | $0.00019 | $0.00173 |
| Sonnet 5 | $0.00008 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
code-documentation-code-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 3d 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
1 near-identical copy found in the catalogue:
- code-documentation-code-explain — 86% identical, 10 lines differ
What it actually says
Code Explanation and Analysis
You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations for developers at all levels.
Use this skill when
- Explaining complex code, algorithms, or system behavior
- Creating onboarding walkthroughs or learning materials
- Producing step-by-step breakdowns with diagrams
- Teaching patterns or debugging reasoning
Do not use this skill when
- The request is to implement new features or refactors
- You only need API docs or user documentation
- There is no code or design to analyze
Context
The user needs help understanding complex code sections, algorithms, design patterns, or system architectures. Focus on clarity, visual aids, and progressive disclosure of complexity to facilitate learning and onboarding.
Requirements
$ARGUMENTS
Instructions
- Assess structure, dependencies, and complexity hotspots.
- Explain the high-level flow, then drill into key components.
- Use diagrams, pseudocode, or examples when useful.
- Call out pitfalls, edge cases, and key terminology.
- If detailed examples are required, open
resources/implementation-playbook.md.
Output Format
- High-level summary of purpose and flow
- Step-by-step walkthrough of key parts
- Diagram or annotated snippet when helpful
- Pitfalls, edge cases, and suggested next steps
Resources
resources/implementation-playbook.mdfor detailed examples and templates.
What ships with it
1 file 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.
- 3d ago First seen · 47 lines · 39 tokens per session scan A 2e27c71cbf47
code-documentation-code-explain is a skill published in the GitHub repository rmyndharis/antigravity-skills (1,449 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 347 once invoked, about $0.0002 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 skills, from other repositories
magi_guide
Answer MAGI usage and troubleshooting questions from the installed manual: look up the exact error in magi guide --symptoms/--search, read the relevant chapter, verify the workspace state, and hand back the exact fix command. Use whenever a magi command errors or the user asks how to install, migrate, ingest, build…
learning-exploration
Group skill: Learning/exploration — deep research, codebase analysis, architecture diagrams, design patterns, practice, notes, and sharing.
understand-explain
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase.
golang-stay-updated
Golang ecosystem watch list — official sources (go.dev/blog, pkg.go.dev, tour.golang.org, golang-nuts), newsletters (Golang Weekly, Awesome Go Newsletter), communities (r/golang, gophers.slack.com, Go Forum, go.dev/wiki), blogs (Dave Cheney, Ardan Labs, Rob Pike), YouTube channels (Gopher Academy, GopherCon EU/UK)…
training-report
Produce a professional training/workshop report as a .docx file. Use this skill whenever the user mentions "training report", "workshop report", "compte rendu", "compte rendu de formation", "formation report", "debriefing a workshop", "write up a training session", "résumé de formation", or any request to document a…
guided-learning
AI-Guided Learning mentor. Guides the user step-by-step to build and learn a new technology without writing the final code for them.