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/cursor-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/cursor-kit/explain)<a href="https://agentmods.dev/commands/duongductrong/cursor-kit/explain"><img src="https://agentmods.dev/badge/commands/duongductrong/cursor-kit/explain/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/commands/duongductrong/cursor-kit/explain"><img src="https://agentmods.dev/badge/commands/duongductrong/cursor-kit/explain.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.00000 | $0.00335 |
| Opus 5.5 | $0.00000 | $0.00134 |
| Sonnet 5.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 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.
This is a copy
100% identical to explain — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 44 lines · 0 tokens per session scan A f5545590fdcc
explain is a command published in the GitHub repository duongductrong/cursor-kit (23 stars, last pushed 7mo 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. It is 100% identical to explain, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
ios-build
Plan, build, test and screenshot a native SwiftUI iOS app from a plain-language description.
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…
analyze-failures
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
test-management
Organize, classify, and trace Katalon True Platform/TestOps test assets. Use when you need to structure test cases into folders and suites, move or reorganize cases, search and find existing assets at scale, link or unlink requirements to test cases, or produce a requirement-to-test traceability report (which…
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…