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-cli-configgit 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-cli-config)<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/update-cli-config"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/update-cli-config/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-cli-config"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/update-cli-config.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 Excessive Agency · line 51 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00912 |
| Opus 5 | $0.00026 | $0.00456 |
| Sonnet 5 | $0.00011 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
update-cli-config 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- update-cli-config — 94% identical, 7 lines differ
- update-cli-config — 94% identical, 4 lines differ
- update-cli-config — 91% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor CLI Configuration
This skill explains how to view and modify Cursor CLI settings stored in ~/.cursor/cli-config.json.
Config File Location
The config file is ~/.cursor/cli-config.json.
Projects can layer overrides via .cursor/cli.json files. The CLI walks from the git root to the current working directory and merges each .cursor/cli.json it finds (deeper files take precedence). Project overrides only affect the current session; they are not written back to the home config.
How to Modify
Read ~/.cursor/cli-config.json, apply changes, and write it back. The file is standard JSON. Changes take effect after restarting the CLI.
Available Settings
permissions (required)
Tool permission rules. Each entry is a string pattern.
allow: string[] — patterns for allowed tool calls (e.g."Shell(**)","Mcp(server-name, tool-name)")deny: string[] — patterns for denied tool calls
editor
vimMode: boolean — enable vim keybindings in the CLI inputdefaultBehavior:"ide"|"agent"— default behavior mode
display (optional)
showLineNumbers: boolean (default: false) — show line numbers in code outputshowThinkingBlocks: boolean (default: false) — show model thinking/reasoning blocksshowStatusIndicators: boolean (default: false) — show status indicators in the UI
channel (optional)
Release channel: "prod" | "staging" | "lab" | "static"
maxMode (optional)
boolean (default: false) — enable max mode for higher-quality model responses
approvalMode (optional)
Controls tool approval behavior:
"allowlist"(default) — require approval for tools not in the allow list"unrestricted"— auto-approve all tool calls (yolo mode)
sandbox (optional)
Sandbox execution environment settings:
mode:"disabled"|"enabled"(default:"disabled")networkAccess:"user_config_only"|"user_config_with_defaults"|"allow_all"— controls network access from sandboxnetworkAllowlist: string[] — domains the sandbox is allowed to reach
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 · 88 lines · 53 tokens per session scan A 0bb1b24caac3
update-cli-config is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (26 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 912 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
inkbox-cli
Use when running or writing shell commands with the Inkbox CLI (inkbox / @inkbox/cli) for identities, email, mailbox imports, phone, text/SMS, iMessage, A2A task/message history, contacts, notes, contact rules, vault, mailbox storage, mail clients (IMAP/SMTP), phone number, webhook, or signup workflows.
instar-session
Spawn, monitor, and communicate with persistent Claude Code sessions running in the background. Use when a task needs to run without blocking the current session, when the user asks to do something in the background, or when a long-running task needs its own context window. Trigger words: background task, spawn…
Gmail, Google Calendar, Drive, Docs, Sheets and Contacts for a connected Google account: read and search mail, send and reply, book and move meetings, find files, read and write Docs and Sheets, look people up. Use whenever the user mentions their email, inbox, calendar, meetings, Drive, a Google Doc or Sheet.
iq
Workspace code search — one call from a question to ranked path:line anchors. Use for definitions, references, natural-language code questions, file skeletons, and git history.
example-notes
Leave a short note for the owner in the Example rail view, using the intentic-example CLI. Use when the user asks you to note, jot, remember or flag something lightweight for them to read later, and when you want to leave a breadcrumb about work you did that has no better home.
peekaboo-snapshot-act
Use when an agent needs to drive a macOS native app reliably — snapshot-then-act via Peekaboo's accessibility-aware element IDs beats screenshot-per-click for any app with proper AX support.