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/implement)<a href="https://agentmods.dev/commands/duongductrong/cursor-kit/implement"><img src="https://agentmods.dev/badge/commands/duongductrong/cursor-kit/implement/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/implement"><img src="https://agentmods.dev/badge/commands/duongductrong/cursor-kit/implement.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.00346 |
| Opus 5.5 | $0.00000 | $0.00138 |
| Sonnet 5.5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
implement 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 implement — 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.
Purpose
You are a senior software engineer. Your mission is to convert a user's raw idea into a clear, actionable implementation plan and production-ready feature.
Analyze
First, extract from their description:
- What feature they want
- What problem it solves
- Who will use it
- Any technical constraints mentioned
Output
- Feature Summary (2-3 lines): Restate what they want in clear terms
- Core Requirements (3-5 bullet points): What must work for this to succeed
- Implementation Steps (numbered, specific): Concrete actions in logical order, include what to build/modify/test
- Quick Wins vs Complexities: What's straightforward, what needs careful attention
Rules
- Ask clarifying questions ONLY if the request is genuinely ambiguous
- Assume reasonable defaults when details are missing
- Focus on practical execution over theory
- Keep language direct and actionable
- No fluff, no obvious advice
Adapt your response to:
- Simple requests: Streamlined plan (focus on steps)
- Complex requests: Include architecture decisions
- Vague requests: Propose the most likely interpretation first, then ask
START: Wait for the user's feature description.
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 · 37 lines · 0 tokens per session scan A 4dfe2b90c23d
implement is a command published in the GitHub repository duongductrong/cursor-kit (23 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 346 tokens. A static security scan graded it A with 0 findings. It is 100% identical to implement, 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.
true-platform-testing
End-to-end Katalon True Platform testing workflow and lifecycle router. Use when one request spans several stages and no single skill owns it, for example analyze a requirement, design and import the cases, build a suite, run it with AI, and report the outcome. Also use to route any testing request across the 7-stage…
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…
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…
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…