agentmods.dev

claude-settings-editor: Instructions file for Claude Code

CLAUDE.md

claude-settings-editor CLAUDE.md is an instructions file for Claude Code from mrspot-dev/claude-settings-editor. It costs 1,099 tokens per session, scanned A, original, MIT.

A browser-based editor for Claude Code settings.json files, with explanations of each setting and visual controls instead of raw JSON. It can write the changes back to the selected file.

In plain words
What is it for?
Use it to inspect and edit Claude Code settings, choose between settings files, and check changes in a Chromium browser. It is a single HTML file with no build step or server.
Why use it?
It reduces the need to understand JSON structure and remember where user, project, and local settings are stored. The included helper script can find those files automatically.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions Claude Code.

This is mrspot-dev/claude-settings-editor's own configuration. It tells Claude Code how to work on claude-settings-editor itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-settings-editor configures →

not rated 5repo 7d ago A scan 1,099 tokens original MIT
View source ↗ mrspot-dev/claude-settings-editor mrspot-dev.github.io
Reuse

Borrowing it

Nothing to install: this file belongs to mrspot-dev/claude-settings-editor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mrspot-dev/claude-settings-editor/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/mrspot-dev/claude-settings-editor

Made for: Claude Code.

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.

agentmods badge for claude-settings-editor CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/mrspot-dev/claude-settings-editor/claude-md/github.svg)](https://agentmods.dev/instructions/mrspot-dev/claude-settings-editor/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/mrspot-dev/claude-settings-editor/claude-md"><img src="https://agentmods.dev/badge/instructions/mrspot-dev/claude-settings-editor/claude-md/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.

agentmods 80×15 button for claude-settings-editor CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/mrspot-dev/claude-settings-editor/claude-md"><img src="https://agentmods.dev/badge/instructions/mrspot-dev/claude-settings-editor/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,099 This file is loaded in full into every session.
When invoked 1,099 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01099 $0.01099
Opus 5 $0.00549 $0.00549
Sonnet 5 $0.00220 $0.00220
Haiku 4.5 $0.00110 $0.00110

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

Security

Grade A, and why

claude-settings-editor CLAUDE.md 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.

CLAUDE.md · 34 lines

How it starts

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

Claude Settings Editor

GUI-Editor für Claude Code settings.json-Dateien. Erklärt jede Einstellung auf Deutsch (UI ist mehrsprachig), erlaubt visuelles Bearbeiten statt Roh-JSON und schreibt die Datei direkt über die File System Access API zurück.

Stack & Struktur

  • Single-File-App: claude-settings-editor.html — kein Build, kein Server, kein package.json. Tailwind CSS via CDN, Alpine.js 3.14 (Reaktivität), JetBrains Mono + DM Sans.
  • open-editor.py / open-editor.bat — Companion-Script, findet User-/Project-/Local-settings.json automatisch und öffnet den Editor pre-loaded (Priorität: Local > Project > User > Defaults).
  • docs/plans/ — Design-/Feature-Abgleich-Dokumente (kein Code).
  • logo.svg, README.md.

Kommandos

  • Öffnen (manuell): claude-settings-editor.html in einem Chromium-Browser öffnen (File System Access API braucht Chromium — Firefox/Safari nicht voll unterstützt).
  • Öffnen (Auto-Detect): python open-editor.py
  • Kein Build-Schritt für Nutzer; Werkzeugkette nur für Pflegende (Tests, Selbst-Check, Generator, siehe unten). UI-Änderungen zusätzlich im Browser verifizieren (Neuladen der HTML-Datei).
  • Tests: node --test tools/*.test.js (Node 26, node:test)
  • Selbst-Check: node tools/self-check.js (Exit 1 bei harten Befunden — vor jedem Commit)
  • Schema-Extrakt erneuern: node tools/build-schema-map.js --fetch (schreibt SCHEMA_MAP in die HTML; tools/sources/settings-reference.md bleibt gitignored)

Constraints & Gotchas

  • 16 Tabs, 6 Sprachen (de, en, es, fr, ja, pt): jedes neue User-facing Text-Element braucht einen Key im T-Objekt in allen 6 Sprachen — nicht nur Deutsch.
  • Jedes neue Setting braucht 4 Stellen: defaultSettings(), cleanJson(), loadJson(), knownKeys — sonst wird es beim Export/Import silent gedroppt (bereits mehrfach passiert, z. B. env-Vars, cleanupPeriodDays).
  • Boolean-Export-Falle: Settings mit Default false (z. B. spinnerTipsEnabled, showTurnDuration) müssen bei true exportiert werden, nicht invertiert — war ein wiederkehrender Bug.
  • Alpine.js-Reaktivität: kein delete-Operator auf reaktiven Objekten verwenden — Object-Reassign-Pattern nutzen, sonst bricht die Reaktivität.
  • Roundtrip-Sicherheit: unbekannte/fremde Properties aus importierten settings.json-Dateien werden über _extraProps erhalten, nicht verworfen — beim Ändern der Import/Export-Logik darauf achten.
  • Permission-Mode-Werte sind Breaking-Change-anfällig: Claude Code hat allowPrompt→default, acceptAll→bypassPermissions umbenannt — bei neuen Claude-Code-Releases aktiv auf weitere Wert-Änderungen prüfen (nicht raten, gegen offizielles JSON-Schema json.schemastore.org/claude-code-settings.json verifizieren).
  • Model-Liste/-Beschreibungen veralten schnell (Claude-Releases sind schneller als der Editor) — vor jedem Feature-Update aktiv nach aktuellen Modell-IDs/Aliasen recherchieren, nicht aus altem Wissen übernehmen.
  • Bei größeren Feature-Batches hat sich das Muster HIVE-Schwarm (Recherche/Bau parallel) + abschließende SENTINEL/Code-Review-Runde bewährt.
  • Schema hinkt dem Changelog hinterher (09/2026: Schema 2.1.219, Changelog 2.1.267): neue Keys wie maxEffortLevel/modelSettings stehen nur im Changelog (raw.githubusercontent.com/anthropics/claude-code/main/CHANGELOG.md) — beide Quellen diffen, nicht nur das Schema.
  • Erfundene Keys nicht stillschweigend behalten: legacyKeys in loadJson() listet Schlüssel, die der Editor früher schrieb, Claude Code aber nie las (releaseChannel, fileSuggestions, autoDreamEnabled, teamateMode). Sie werden beim Import mit Hinweis verworfen statt über _extraProps zurückgeschrieben; Wert-Migrationen (Typo, Groß-/Kleinschreibung) direkt daneben.
  • Datei ist durchgehend CRLF — Patch-Skripte erst normalisieren (LF), am Ende zurück; grep -c zählt Zeilen, nicht Vorkommen (grep -o | wc -l).
  • Neue Keys: zusätzlich zu den 4 Stellen muss der Key in SCHEMA_MAP existieren (sonst schlägt self-check an) — erfundene Keys fallen damit auf.

Read the full file on GitHub · 34 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.

  1. 6d ago First seen · 34 lines · 1,099 tokens per session scan A cd26361fa65a

Subscribe to this mod's changes

claude-settings-editor CLAUDE.md is an instructions file published in the GitHub repository mrspot-dev/claude-settings-editor (5 stars, last pushed 7d ago), licensed MIT. It adds 1,099 tokens to every session, about $0.0055 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-11.

Productivityanthropic-claudeclaude-settingsclaude-settings-editorclaudecodeeditorgui
Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 8,838 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,126 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens