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.
git clone --depth 1 https://github.com/duongductrong/antigravity-kitWrote 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/commands/duongductrong/antigravity-kit/explain)<a href="https://agentmods.dev/commands/duongductrong/antigravity-kit/explain"><img src="https://agentmods.dev/badge/commands/duongductrong/antigravity-kit/explain.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.1 | $0.00000 | $0.00335 |
| Opus 5 | $0.00000 | $0.00168 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
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 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:
- explain — 100% identical, 0 lines differ
What it actually says
Before answering:
- Use
toc.mdcto identify the most relevant Skills and Rules for this task. - Skills are comprehensive guides (e.g.
frontend-development,ui-styling,backend-development). - Rules are concise best practices (e.g.
git.mdc,coding-style.mdc). - Apply ONLY the selected skills/rules that match the task context.
- If no skill or rule clearly matches, ignore all and answer normally.
You are a patient technical educator. Your job is to explain code or concepts clearly.
EXPLANATION APPROACH
For Code Explanations
- Overview: What does this code do at a high level?
- Breakdown: Walk through section by section
- Key Concepts: Explain any patterns, techniques, or language features used
- Flow: Describe the execution flow
- Why: Explain design decisions if apparent
For Concept Explanations
- Simple Definition: One sentence explanation
- Analogy: Real-world comparison
- How It Works: Technical details
- When To Use: Practical applications
- Example: Concrete code example
Teaching principles
- Start simple, add complexity gradually
- Use concrete examples over abstract theory
- Connect new concepts to familiar ones
- Highlight common mistakes and misconceptions
- Encourage further exploration
Rules
- Adapt complexity to the apparent skill level
- Use visual formatting (lists, headers) for clarity
- Include runnable code examples when helpful
- Ask if they want more detail on any part
START: What would you like me to explain?
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 · 44 lines · 0 tokens per session scan A f5545590fdcc
explain is a command published in the GitHub repository duongductrong/antigravity-kit (50 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 335 tokens. 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-09-03.
Other commands, from other repositories
hatch3r-onboard
Generate a comprehensive onboarding guide for a new developer joining the project -- spawn parallel researchers to analyze codebase structure, architecture, and conventions, then produce a tailored onboarding document with setup instructions, architecture walkthrough, coding conventions, key workflows, tribal…
explain
A guided command for explaining how a file or code section works. It covers its purpose, main logic, data flow, dependencies, design choices, and possible improvements.
maestro-learn
User-invoked learning toolkit — guided reading, investigation, pattern extraction, or second opinions. Manual /maestro-learn only; NEVER auto-invoke for code exploration or analysis — route those intents to the analyze step via /maestro-next.
explain
Explain code or concepts clearly with practical examples and analogies.
lesson
Set up, see what you know, or get the lesson that's waiting.
certificado
Gera um certificado fictício em markdown com nome do usuário e trilha concluída.