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 skills add kensaurus/cursor-kenji --skill update-cursor-settingsgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/update-cursor-settings)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/update-cursor-settings"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/update-cursor-settings/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/skills/kensaurus/cursor-kenji/update-cursor-settings"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/update-cursor-settings.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.00066 | $0.01095 |
| Opus 5.5 | $0.00026 | $0.00438 |
| Sonnet 5.5 | $0.00013 | $0.00219 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade A, and why
update-cursor-settings 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
86% identical to update-cursor-settings — 39 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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Updating Cursor Settings
This skill guides you through modifying Cursor/VSCode user settings. Use this when the user wants to change editor settings, preferences, configuration, themes, keybindings, or any settings.json values.
Check existing first
Before modifying settings, check:
- Read current settings:
cat ~/.config/Cursor/User/settings.json 2>/dev/null | head -50 # Linux
cat ~/Library/Application\ Support/Cursor/User/settings.json 2>/dev/null | head -50 # macOS
- Check for workspace settings:
cat .vscode/settings.json 2>/dev/null
- Understand current state:
- What's the current value of the setting?
- Are there conflicting workspace settings?
Why: Preserve existing settings. Only modify what's requested.
Settings File Location
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Cursor/User/settings.json |
| Linux | ~/.config/Cursor/User/settings.json |
| Windows | %APPDATA%\Cursor\User\settings.json |
Before Modifying Settings
- Read the existing settings file to understand current configuration
- Preserve existing settings - only add/modify what the user requested
- Validate JSON syntax before writing to avoid breaking the editor
Modifying Settings
Step 1: Read Current Settings
// Read the settings file first
const settingsPath = "~/Library/Application Support/Cursor/User/settings.json";
// Use the Read tool to get current contents
Step 2: Identify the Setting to Change
Common setting categories:
- Editor:
editor.fontSize,editor.tabSize,editor.wordWrap,editor.formatOnSave - Workbench:
workbench.colorTheme,workbench.iconTheme,workbench.sideBar.location - Files:
files.autoSave,files.exclude,files.associations - Terminal:
terminal.integrated.fontSize,terminal.integrated.shell.* - Cursor-specific: Settings prefixed with
cursor.oraipopup.
Step 3: Update the Setting
When modifying settings.json:
- Parse the existing JSON (handle comments - VSCode settings support JSON with comments)
- Add or update the requested setting
- Preserve all other existing settings
- Write back with proper formatting (2-space indentation)
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 Changed · +1 lines 1190373b6718
- 1mo ago Changed 3330673ef2b6
- 1mo ago First seen · 137 lines · 66 tokens per session scan A 5454e777fe9e
update-cursor-settings is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 29d ago), licensed MIT. It adds 66 tokens to every session and 1,095 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to update-cursor-settings, differing in 39 lines, and is treated as a copy.
Other skills, from other repositories
noteplan
Read, search, create, and edit NotePlan notes and daily logs directly via the filesystem. Use this skill whenever the user references NotePlan, daily notes, weekly notes, project notes, or wants to check/update their planning. Triggers: 'noteplan', 'daily note', 'today's note', 'weekly note', 'check my notes', 'add to…
lno-task-prioritization
Classify tasks as Leverage, Neutral, or Overhead using Shreyas Doshi's LNO framework to maximize impact and reduce stress. Use when the user is planning their week, feeling overwhelmed, prioritizing a to-do list, doing sprint planning, or asking how to spend their time more effectively.
dynamic-context
Use when managing context window to optimize token usage and prevent context bloat.
cursor-delegate
Delegate bounded light-to-medium implementation, investigation, documentation, configuration, testing, and tooling work to Cursor Bridge after the primary agent owns direction and risk boundaries. Also use when the user explicitly asks to create, keep, continue, inspect, or close the same Cursor execution session…
agent-work-receipt
Produces a conservative agent work receipt after completed work: finished output, time estimates, review burden, risks, and value judgment. Use when the user invokes /agent-work-receipt, asks for a work receipt, or wants to measure agent productivity honestly after a session.
hot-reload-optimizer
Optimizes hot module replacement and fast refresh for development speed with Vite, Next.js, and webpack configurations. Use when users request "hot reload", "HMR optimization", "fast refresh", "dev server speed", or "development performance".