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 robotaitai/project-bedrock --skill update-cursor-settingsgit clone --depth 1 https://github.com/robotaitai/project-bedrockWrote 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/robotaitai/project-bedrock/update-cursor-settings)<a href="https://agentmods.dev/skills/robotaitai/project-bedrock/update-cursor-settings"><img src="https://agentmods.dev/badge/skills/robotaitai/project-bedrock/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/robotaitai/project-bedrock/update-cursor-settings"><img src="https://agentmods.dev/badge/skills/robotaitai/project-bedrock/update-cursor-settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 54 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.5 | $0.00021 | $0.00409 |
| Sonnet 5.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 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- update-cursor-settings — 100% identical, 0 lines differ
- update-cursor-settings — 100% identical, 0 lines differ
- update-cursor-settings — 100% identical, 0 lines differ
- update-cursor-settings — 86% identical, 39 lines differ
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.
- 1mo ago First seen · 123 lines · 53 tokens per session scan A 8b5ee1a74dc9
update-cursor-settings is a skill published in the GitHub repository robotaitai/project-bedrock (45 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 1,023 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…