Agent skill

Settings Management

by CodeAlive-AI in CodeAlive-AI/ai-driven-development

View and configure settings for coding agents (Claude Code, Codex CLI, OpenCode, Devin CLI/Desktop, and others).

MITAuto-check: notesAgent Workflows

Install Settings Management

skills CLI
$ npx skills add CodeAlive-AI/ai-driven-development --skill settings-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install CodeAlive-AI/ai-driven-development settings-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-development.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/settings-management .claude/skills/settings-management && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
settings-management
GitHub stars
158
Token cost
~1.9k tokens
SKILL.md length
511 words
Files
5 (incl. references)
Skills in repo
22
Repo updated
First seen
Licence
MIT

At a glance

View and configure settings for coding agents (Claude Code, Codex CLI, OpenCode, Devin CLI/Desktop, and others).

  • Works in 6 steps: Determine scope: Ask user which scope… → Read existing settings: Always read… → Merge changes: Preserve existing… → …
  • Tasks that involve Subagents
  • SKILL.md covers Settings File Locations, Quick Actions, Common Configuration Tasks and Scope Selection Guide, plus 5 more sections
  • Calls codex; reaches opencode.ai

What it does

Settings Management is an agent skill from CodeAlive-AI/ai-driven-development. View and configure settings for coding agents (Claude Code, Codex CLI, OpenCode, Devin CLI/Desktop, and others). Covers JSON settings for Claude Code and Devin, TOML for Codex CLI, and JSON/JSONC for OpenCode, including permissions, sandbox, model selection, profiles, feature flags, providers, hooks, subagents, and skills.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/claude-settings.md`, `references/codex-settings.md` and `references/devin-settings.md`).

It sits in Agent Workflows, covering Subagents. The repository describes itself as: Practices, protocols, and skills for AI-driven software development. Skills and safety hooks for Claude Code, Codex, OpenCode, Cursor, Antigravity, and any agent supporting the… The licence is MIT.

When your agent uses it

  • Tasks that involve Subagents

Example prompts

  • “/settings-management”

Requirements

  • Docker

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Determine scope: Ask user which scope (user/project/local) if not specified
  2. Read existing settings: Always read current file before modifying
  3. Merge changes: Preserve existing settings, only modify requested keys
  4. Validate JSON: Ensure valid JSON before writing
  5. Confirm changes: Show user the final settings
  6. Remind to restart: Tell user to restart Claude Code for changes to take effect

What it can do on your machine

Read from SKILL.md and the folder at commit 4cfeb10. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • codex

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • opencode.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Settings Management loads about 1.9k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 511 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:56
    "deny": ["Read(.env)", "Read(.env.*)", "WebFetch"],
  • NoteMentions a .env fileSKILL.md:195
    "ask": ["Write(**/.env*)"]

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CodeAlive-AI/ai-driven-development at commit 4cfeb10, republished under its MIT licence (© CodeAlive-AI). 511 words, ~1,858 tokens.

Download SKILL.mdSave it as .claude/skills/settings-management/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
settings-management
description
View and configure settings for coding agents (Claude Code, Codex CLI, OpenCode, Devin CLI/Desktop, and others). Covers JSON settings for Claude Code and Devin, TOML for Codex CLI, and JSON/JSONC for OpenCode, including permissions, sandbox, model selection, profiles, feature flags, providers, hooks, subagents, and skills.

Settings Management

Manage configuration for coding agents.

IMPORTANT: After modifying settings, always inform the user that they need to restart the agent for changes to take effect. Most settings are only loaded at startup.

Settings File Locations

ScopeLocationShared with team?
User~/.claude/settings.jsonNo
Project.claude/settings.jsonYes (committed)
Local.claude/settings.local.jsonNo (gitignored)
ManagedSystem-level managed-settings.jsonIT-deployed

Precedence (highest to lowest): Managed → Command line → Local → Project → User

Quick Actions

View Current Settings
bash
cat ~/.claude/settings.json 2>/dev/null || echo "No user settings"
cat .claude/settings.json 2>/dev/null || echo "No project settings"
cat .claude/settings.local.json 2>/dev/null || echo "No local settings"
Create/Edit Settings

Use the Edit or Write tool to modify settings files. Always read existing content first to merge changes.

Common Configuration Tasks

Set Default Model
json
{
  "model": "claude-opus-4-7",
  "effort": "high"
}

Effort levels: low, medium, high, xhigh (Opus 4.7 only), max. As of 2026, default effort is high for API-key, Bedrock/Vertex/Foundry, Team, and Enterprise users.

Configure Permissions
json
{
  "permissions": {
    "allow": ["Bash(npm run:*)", "Bash(git:*)"],
    "deny": ["Read(.env)", "Read(.env.*)", "WebFetch"],
    "defaultMode": "acceptEdits"
  }
}

defaultMode accepts: default, acceptEdits, plan, auto, dontAsk, bypassPermissions. The new auto mode (March 2026) uses an LLM-based classifier and triggers PermissionDenied hooks on rejection.

Add Environment Variables
json
{
  "env": {
    "MY_VAR": "value",
    "CLAUDE_CODE_ENABLE_TELEMETRY": "1"
  }
}
Enable Extended Thinking
json
{
  "alwaysThinkingEnabled": true
}
Configure Attribution
json
{
  "attribution": {
    "commit": "Generated with AI\n\nCo-Authored-By: AI <ai@example.com>",
    "pr": ""
  }
}
Configure Sandbox
json
{
  "sandbox": {
    "enabled": true,
    "autoAllowBashIfSandboxed": true,
    "excludedCommands": ["docker", "git"]
  }
}
Configure Hooks
json
{
  "hooks": {
    "PreToolUse": {
      "Bash": "echo 'Running command...'"
    }
  }
}

Scope Selection Guide

  • User settings (~/.claude/settings.json): Personal preferences across all projects
  • Project settings (.claude/settings.json): Team-shared settings, commit to git
  • Local settings (.claude/settings.local.json): Personal project overrides, not committed

Workflow

  1. Determine scope: Ask user which scope (user/project/local) if not specified
  2. Read existing settings: Always read current file before modifying
  3. Merge changes: Preserve existing settings, only modify requested keys
  4. Validate JSON: Ensure valid JSON before writing
  5. Confirm changes: Show user the final settings
  6. Remind to restart: Tell user to restart Claude Code for changes to take effect

Codex CLI Settings

Codex uses TOML format in ~/.codex/config.toml (user) and .codex/config.toml (project, trusted projects only).

toml
model = "gpt-5.5"                  # As of April 2026; gpt-5.4 is a valid fallback
approval_policy = "on-request"     # untrusted | on-request | never (or { granular = { ... } })
                                    # NOTE: "on-failure" is DEPRECATED — migrate to on-request or never
sandbox_mode = "workspace-write"   # read-only | workspace-write | danger-full-access

[features]
codex_hooks = true                 # Lifecycle hooks (stable in v0.124, April 2026)
multi_agent = true                 # Subagent orchestration (GA March 2026)

Key differences from Claude Code:

  • TOML format instead of JSON; project config requires explicit trust
  • Starlark rules for command policies in .codex/rules/
  • Named profiles ([profiles.NAME]) for different workflows
  • Feature flags system (codex features list, codex --enable feature)
  • Lifecycle hooks live inline as [[hooks.PreToolUse]] (etc.) blocks in config.toml
  • [agents] block for subagent orchestration (max_threads, max_depth)
  • [[skills.config]] for per-skill enable/disable overrides
  • Custom model providers via [model_providers.NAME], including amazon-bedrock since v0.123

See references/codex-settings.md for the full Codex config reference (covers approval/sandbox/profiles/features/agents/skills/hooks/rules/providers/admin enforcement).

Show full SKILL.md (166 more words)Show less

OpenCode Settings

OpenCode (anomalyco/opencode v1.14.x) uses JSON/JSONC in ~/.config/opencode/opencode.json (user) and opencode.json (project root, or under .opencode/).

json
{
  "$schema": "https://opencode.ai/config.json",
  "model": "anthropic/claude-sonnet-4-5",
  "permission": {
    "edit": "ask",
    "bash": { "*": "ask", "git status *": "allow" }
  },
  "instructions": ["AGENTS.md", "docs/style.md"]
}

Key differences from Claude Code:

  • Schema-validated JSON/JSONC, not plain JSON
  • Configs are deep-merged (later wins; arrays like instructions are concatenated, not replaced)
  • Permissions are an object of allow/ask/deny per tool with glob patterns, not separate allow/deny/ask arrays
  • Theme/keybinds live in a separate tui.json file
  • Multi-provider via model: "<provider>/<model-id>" and a top-level provider block
  • Variable substitution: {env:VAR} and {file:path}

See references/opencode-settings.md for full OpenCode config reference.

Devin CLI / Desktop Settings

Devin uses JSON in ~/.config/devin/config.json (user; %APPDATA%\devin\config.json on Windows), .devin/config.json (project), and .devin/config.local.json (project-local, gitignored). MCP servers live in dedicated mcp_config.json files at the same levels.

json
{
  "agent": { "model": "swe-2-high" },
  "permissions": {
    "allow": ["Read(**)", "Exec(git)"],
    "ask": ["Write(**/.env*)"]
  },
  "read_config_from": { "claude": true, "cursor": true, "windsurf": true }
}

Key differences:

  • Project configs accept only permissions, read_config_from, and hooks
  • read_config_from imports rules/hooks/subagents from .claude/, .cursor/, .windsurf/ by default
  • Skills: .devin/skills/ (project), ~/.config/devin/skills/ (user)
  • Plugins: .devin-plugin/plugin.json manifest; devin plugins CLI

See references/devin-settings.md for the full Devin config reference.

Reference

© CodeAlive-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/settings-management of CodeAlive-AI/ai-driven-development.

  • SKILL.md
  • references/claude-settings.md
  • references/codex-settings.md
  • references/devin-settings.md
  • references/opencode-settings.md

Open the folder on GitHubat commit 4cfeb10

Compare with similar skills

Settings Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Settings Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Settings Management this skillCodeAlive-AI/ai-driven-development158—~1.9kAutomated safety check: NotesMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k7 repos~2.8kAutomated safety check: PassApache-2.0
Subagent Driven DevelopmentAsvarox/allkaraoke26137 repos~1.2kAutomated safety check: PassNone
Dispatching Parallel Agentsultralisp/ultralisp25840 repos~1.5kAutomated safety check: PassNone
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence
Task Observerrebelytics/one-skill-to-rule-them-all3.2k1 repos~12kAutomated safety check: PassCC-BY-4.0

Similar skills

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 37 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Dispatching Parallel Agents

    ultralisp/ultralisp

    A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    258 GitHub starsUsed in 40 repos~1.5k tokens
    Agent WorkflowsAuto-check passed
  • Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed
  • Task Observer

    rebelytics/one-skill-to-rule-them-all

    Monitors task execution for skill improvement opportunities.

    3.2k GitHub starsUsed in 1 repo~12k tokens
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from CodeAlive-AI/ai-driven-development

All 22 skills in this repo
  • Investigating Repository History

    CodeAlive-AI/ai-driven-development

    Investigate GitHub repository history before risky code changes using git blame/log, GitHub PRs, review comments, squash/rebase/cherry-pick/rename heuristics, and cited evidence.

    158 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Plugins Management

    CodeAlive-AI/ai-driven-development

    Create, publish, delete, and submit plugins for coding agents (Claude Code, OpenCode, Devin CLI/Desktop).

    158 GitHub stars~3.1k tokensUpdated today
    Auto-check: notes
  • Windows QA Engineer

    CodeAlive-AI/ai-driven-development

    A skill your agent uses when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP.

    158 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Agentic Readiness

    CodeAlive-AI/ai-driven-development

    Audit and improve repositories for reliable agentic work across Codex and Codex App, Claude Code, and OpenCode.

    158 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Hooks Management

    CodeAlive-AI/ai-driven-development

    Manage hooks and automation for coding agents (Claude Code, Codex CLI, OpenCode, Devin CLI/Desktop).

    158 GitHub stars~4.8k tokensUpdated today
    Auto-check: notes
  • Semantic Scholar Deep

    CodeAlive-AI/ai-driven-development

    Deep research over the Semantic Scholar Graph API. An agent skill from CodeAlive-AI/ai-driven-development.

    158 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Settings Management

What does Settings Management do?

View and configure settings for coding agents (Claude Code, Codex CLI, OpenCode, Devin CLI/Desktop, and others). Settings Management is an agent skill from CodeAlive-AI/ai-driven-development. View and configure settings for coding agents (Claude Code, Codex CLI, OpenCode, Devin CLI/Desktop, and others).

When should I use Settings Management?

Settings Management fits situations like: tasks that involve Subagents.

How do I install Settings Management in Claude Code?

Run `npx skills add CodeAlive-AI/ai-driven-development --skill settings-management -a claude-code`. Or copy the skill folder (skills/settings-management in CodeAlive-AI/ai-driven-development) into .claude/skills/settings-management in your project. Claude Code loads it when a task matches its description.

How do I install Settings Management in Codex?

Run `npx skills add CodeAlive-AI/ai-driven-development --skill settings-management -a codex`. Or copy the skill folder (skills/settings-management in CodeAlive-AI/ai-driven-development) into .agents/skills/settings-management in your project. Codex loads it when a task matches its description.

Can I use Settings Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CodeAlive-AI/ai-driven-development --skill settings-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/settings-management, .gemini/skills/settings-management, .github/skills/settings-management and .opencode/skills/settings-management in your project.

What does Settings Management need to run?

Going by SKILL.md and its folder, Settings Management needs the command-line tools its instructions call (codex). Our summary lists: Docker.

Does Settings Management access the network?

SKILL.md names 1 domain. In commands or code: opencode.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Settings Management safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Settings Management use?

Settings Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Settings Management use?

About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.

What are the alternatives to Settings Management?

Skills that share tags, products or a category with Settings Management: Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Settings Management?

CodeAlive-AI (a GitHub organization) maintains it in CodeAlive-AI/ai-driven-development, which has 158 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 8, 2026.

Source: CodeAlive-AI/ai-driven-development on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.