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 Kevin-Liu-01/Agent-Machines --skill update-cursor-settingsgit clone --depth 1 https://github.com/Kevin-Liu-01/Agent-MachinesWrote 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/kevin-liu-01/agent-machines/update-cursor-settings)<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/update-cursor-settings"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/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/kevin-liu-01/agent-machines/update-cursor-settings"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/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.00053 | $0.01023 |
| Opus 5 | $0.00026 | $0.00511 |
| Sonnet 5 | $0.00011 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00102 |
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 6d 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 update-cursor-settings — 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.
How it starts
The opening of the file, as written. The whole thing — 123 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 you want to change editor settings, preferences, configuration, themes, keybindings, or any settings.json values.
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)
Example: Changing Font Size
If user says "make the font bigger":
{
"editor.fontSize": 16
}
Example: Enabling Format on Save
If user says "format my code when I save":
{
"editor.formatOnSave": true
}
Example: Changing Theme
If user says "use dark theme" or "change my theme":
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.
- 6d ago First seen · 123 lines · 53 tokens per session scan A 8b5ee1a74dc9
update-cursor-settings is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (27 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,023 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to update-cursor-settings, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
holix-cron
Schedule recurring agent tasks via Holix built-in gateway cron (not crontab or custom scripts).
21-day-self-interview
A 21-night guided self-reflection routine in which an agent asks three questions each night, remembers the answers, and reflects on them at key points.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
remindme
⏰ simple Telegram reminders for OpenClaw. cron, zero dependencies.
email-formatting
Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house style.
json-schema-emails
Canonical shape of the .workflow/emails/emails.json file passed between the fetch and summarize states — required fields (sender, recipient, subject, date, body), types, and field semantics. Read this whenever you write or read emails.json so producer and consumer agree on the shape.