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 skills/patrick-fu/awesome-skills/cursor-coding-agentnpx skills add patrick-fu/awesome-skills --skill cursor-coding-agentgit clone --depth 1 https://github.com/patrick-fu/awesome-skillsWrote 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/skills/patrick-fu/awesome-skills/cursor-coding-agent)<a href="https://agentmods.dev/skills/patrick-fu/awesome-skills/cursor-coding-agent"><img src="https://agentmods.dev/badge/skills/patrick-fu/awesome-skills/cursor-coding-agent.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.00022 | $0.00723 |
| Opus 5 | $0.00011 | $0.00362 |
| Sonnet 5 | $0.00004 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
cursor-coding-agent 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Coding Agent
Use Cursor CLI only after the user or active workflow explicitly selects it as the external executor.
Minimal Workflow
- Set
<launcher>to the requested Cursor binary, absolute path, alias, or wrapper. Verify<launcher> --versionidentifies Cursor because the generic command nameagentcan resolve to another product. Preserve a provided wrapper; it may inject model, authentication, or permission settings, including bypass permissions. - Run
<launcher> --helpbefore composing version-sensitive flags. Use model listing or subcommand help only when needed. - Choose the model and thinking effort deliberately, following the guidance below and the choices currently exposed by the launcher.
- Use monitor mode by default for any task that may take time. Use final mode only when the task is clearly trivial and short.
- Run from the intended repository or workspace, pass a bounded task contract, and wait for the external process to finish.
- Inspect the resulting diff, tests, and final answer before claiming success.
Model and Effort
Honor explicit model or effort choices. Otherwise inspect current help and the current account's model list before launching:
- For routine, bounded work, prefer a balanced model and moderate effort.
- For deep review, ambiguous debugging, cross-module design, or other high-risk work, prefer a frontier model and high or maximum supported effort.
- Use the highest tier only when its quality benefit justifies the extra latency or cost, and after checking whether that tier has additional behavior.
Do not hardcode model names or effort levels from this skill; the launcher's current help and model list are authoritative.
Monitor Mode (Default)
Use Cursor's semantic JSON stream without requesting partial assistant output:
<launcher> --print --trust --output-format stream-json "Your task"
Start the command with the host's long-running process facility. Keep the task ID returned by the host, then use the host's wait, poll, or resume facility to read only newly available output while the process runs.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 89 lines · 22 tokens per session scan A 0b4891d2d169
cursor-coding-agent is a skill published in the GitHub repository patrick-fu/awesome-skills (57 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 723 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…