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/duongductrong/cursor-kit/tocgit 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.00418 | $0.00418 |
| Opus 5 | $0.00209 | $0.00209 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
toc 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
You have multiple specialized rules organized into Skills (comprehensive guides with references) and Rules (concise best practices).
Skills
- Aesthetic - Visual design principles, storytelling, and micro-interactions for distinctive interfaces
- Backend Development - API design, architecture, authentication, security, and DevOps patterns
- Frontend Design - Create distinctive, production-grade interfaces with bold aesthetics (avoid generic AI slop)
- Frontend Development - React/TypeScript patterns: Suspense, lazy loading, TanStack Query/Router, MUI v7, file organization
- UI Styling - shadcn/ui components, Tailwind CSS utilities, theming, accessibility, and canvas-based visual design
- Sequential Thinking - Structured problem-solving with revision, branching, and hypothesis verification
- Problem Solving - Techniques for complexity spirals, innovation blocks, meta-patterns, and scale testing
- Research - Systematic research methodology for technical solutions with report generation
Rules
- Git - Git commit and branching conventions
- Coding Style - Coding style and best practices
Routing Guidelines
- For each user request, first infer which domains are relevant.
- Select 0–3 rules/skills that best match the request, prefer the SINGLE most specific one when possible.
- If both security and performance apply, prioritize
security.mdcfirst, thenperformance.mdc. - If no rule clearly matches, ignore all rules and answer normally.
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 · 29 lines · 418 tokens per session scan A 3418668e2bbe
toc is a cursor rule published in the GitHub repository duongductrong/cursor-kit (21 stars, last pushed 5mo ago), licensed MIT. It adds 418 tokens to every session, about $0.0021 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-30.
Other cursor rules, from other repositories
vibeflow
Vibeflow spec-driven development methodology — guardrails, pipeline, and project knowledge system.
designer
Cursor rule "designer" from ulises-jeremias/agent-toolkit, covering designer, when invoked, design routing — canonical (do not run mechanically), figma subtree and delegate to skills.
test-estimation
Estimate testing effort, duration, and resourcing for a Katalon True Platform/TestOps cycle. Use when the question is how long testing will take, how many testers it needs, whether the scope fits the sprint window, or what a scope change costs in person-hours. Sizes design, manual execution, automated execution and…
exploratory-charter
Write, run, and debrief exploratory testing charters against Katalon True Platform/TestOps when there is no script to follow. Use when you need to turn a vague area into a charter (mission, areas, oracles, timebox), run a timeboxed unscripted session, log what you find as session notes, judge which findings are real…
create-test-cases
Create, update, organize, and link Katalon True Platform/TestOps manual test cases from a synced requirement key such as CEL-6, a read requirement, or free-text product behavior. Use when you need to analyze requirements, design manual test cases using ISTQB techniques as a reference, check existing Katalon coverage…
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…