A command for viewing and changing project-planning settings such as workflow mode, planning detail, automatic commits, tests, and verification.

Use it to inspect settings, change individual options, or restore default planning settings.

It puts planning preferences in one configuration file so the project workflow can be adjusted without editing configuration by hand.

settings — Command for Claude Code by boparaiamrit

Install

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.

Clone the repo

git clone --depth 1 https://github.com/boparaiamrit/skills-by-amrit

Made for: Claude Code.

Or install skills-by-amrit, the plugin that ships this one along with the rest of its 33 skills, 34 commands, 9 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/settings/github.svg)](https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/settings)

Your own site

<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/settings"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/settings"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 756 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00018	$0.00756
Opus 5	$0.00009	$0.00378
Sonnet 5	$0.00004	$0.00151
Haiku 4.5	$0.00002	$0.00076

Measured 10d ago against content hash a6ae4086159a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

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 10d 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.

commands/settings.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

`/settings` — Project Configuration

View and modify the .planning/config.json that controls how planning and execution behave.

Usage

/settings              — Show current settings
/settings set <key> <value> — Change a setting
/settings reset        — Reset to defaults

Available Settings

Mode

node planning-tools.cjs config get mode
node planning-tools.cjs config set mode interactive   # Ask before each step
node planning-tools.cjs config set mode auto           # Auto-advance through steps

Depth

node planning-tools.cjs config get depth
node planning-tools.cjs config set depth quick           # Minimal planning, maximum speed
node planning-tools.cjs config set depth standard         # Balanced (default)
node planning-tools.cjs config set depth comprehensive    # Maximum detail, full research

Workflow Preferences

# Auto-commit after each task
node planning-tools.cjs config set preferences.auto_commit true

# Auto-run tests during execution
node planning-tools.cjs config set preferences.auto_test true

# Require verification before marking tasks done
node planning-tools.cjs config set preferences.verification_required true

# Run research before planning
node planning-tools.cjs config set preferences.research_before_planning true

# Validate plan structure before execution
node planning-tools.cjs config set preferences.plan_check_before_execute false

# Auto-advance to next phase when current completes
node planning-tools.cjs config set preferences.auto_advance_phases false

# Include .planning/ in git commits
node planning-tools.cjs config set preferences.commit_planning_docs true

Settings Reference

Key	Values	Default	Description
`mode`	interactive, auto	interactive	How much user confirmation is needed
`depth`	quick, standard, comprehensive	standard	How thorough planning/research is
`preferences.auto_commit`	true/false	false	Auto-commit after each task
`preferences.auto_test`	true/false	true	Auto-run tests during execution
`preferences.verification_required`	true/false	true	Must verify before marking done
`preferences.research_before_planning`	true/false	true	Run research step before planning
`preferences.plan_check_before_execute`	true/false	false	Validate plan XML before executing
`preferences.auto_advance_phases`	true/false	false	Auto-advance phases on completion
`preferences.commit_planning_docs`	true/false	true	Commit .planning/ to git

Read the full file on GitHub · 105 lines

Changes

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.

10d ago First seen · 105 lines · 18 tokens per session scan A a6ae4086159a

Subscribe to this mod's changes

settings is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 756 once invoked, about $0.0001 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-08-31.

Planning

settings

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

`/settings` — Project Configuration

Usage

Available Settings

Mode

Depth

Workflow Preferences

Settings Reference

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement

settings

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/settings — Project Configuration

Usage

Available Settings

Mode

Depth

Workflow Preferences

Settings Reference

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement

`/settings` — Project Configuration