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 commands/duongductrong/cursor-kit/explaingit clone --depth 1 https://github.com/duongductrong/cursor-kitWhat 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.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 2d 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.
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.
- 2d ago First seen · 44 lines · 0 tokens per session scan A f5545590fdcc
explain is a command published in the GitHub repository duongductrong/cursor-kit (21 stars, last pushed 5mo 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-08-30.
Other commands, from other repositories
mode
Run the workflow in docs/playbooks/mode.md: read the current mode from PROJECT.md, confirm the trade-off of the target mode in one line, update the Mode field and Current mode: line in PROJECT.md, and confirm the new rules. Modes: guided (I write all code), collab (split), autopilot (you write it and teach). Full…
tutorial
Interactive tutorial for learning the plugin. Walks through agents, skills, hooks, and commands with hands-on examples.
pm-review
Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.
learn
Command "learn" from chohra-med/expo_boilerplate, covering command: learn — the learning loop (feedback → rules), when to run it, invocation, the loop (6 steps) and 1 — capture.
optimize
Command "optimize" from doccker/cc-use-exp, covering 第 0 步：范围选择, 统计文件数和行数, 第 1 步：项目画像, 扫描内容 and 输出格式.
design
技术设计（doc 文档框架 / checklist 质量检查）.