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 rules/votruongdanh/skills-agent/explaingit clone --depth 1 https://github.com/VoTruongDanh/Skills-AgentWrote 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/rules/votruongdanh/skills-agent/explain)<a href="https://agentmods.dev/rules/votruongdanh/skills-agent/explain"><img src="https://agentmods.dev/badge/rules/votruongdanh/skills-agent/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 | $0.00059 | $0.00976 |
| Opus 5 | $0.00030 | $0.00488 |
| Sonnet 5 | $0.00012 | $0.00195 |
| Haiku 4.5 | $0.00006 | $0.00098 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Protocol
START: Read .ai-memory.md from project root. Check tech stack, architecture notes, past explanations, and domain context.
END: Update .ai-memory.md using Memory Compaction Rules with: what was explained, key insights, misconceptions clarified, and follow-ups.
Goal
Help the user deeply understand code, logic, architecture, or behavior — at the level of detail they need.
Agent Routing
- If explaining backend/API logic → read
.kiro/skills/agents/agents/backend-specialist.mdand apply its knowledge - If explaining UI/component behavior → read
.kiro/skills/agents/agents/frontend-specialist.mdand apply its knowledge - If explaining database schema/queries → read
.kiro/skills/agents/agents/database-architect.mdand apply its knowledge - If explaining security mechanisms → read
.kiro/skills/agents/agents/security-auditor.mdand apply its knowledge - Default → read
.kiro/skills/agents/agents/documentation-writer.mdfor clear, structured explanation
Socratic Gate
Before explaining, verify:
- Which file, function, or code block should be explained?
- What level of detail? (high-level overview vs line-by-line walkthrough)
- What is the user's familiarity level with this area? If any answer is unclear, ASK before proceeding.
Workflow
- Read Memory — Load
.ai-memory.mdfor project context, tech stack, and architecture. - Read the target code thoroughly — understand intent, not just syntax.
- Identify the explanation scope: single function, module, data flow, or architecture.
- Explain at the requested level:
- High-level: Purpose, inputs/outputs, how it fits in the system.
- Detailed: Step-by-step logic, control flow, edge cases, design decisions.
- Line-by-line: What each line does and why.
- Highlight non-obvious logic, hidden side effects, and design trade-offs.
- Use analogies or diagrams if the concept is complex.
- Suggest follow-up topics if relevant (e.g., "you may also want to understand X").
- Quality Gate — Read
.kiro/skills/_scripts/checklist.mdfor cross-cutting checks. - Update Memory — Save explanation context and insights to
.ai-memory.md.
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.
- 4d ago First seen · 75 lines · 59 tokens per session scan A 6d31249abe35
explain is a cursor rule published in the GitHub repository VoTruongDanh/Skills-Agent (2 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 976 once invoked, about $0.0003 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.