settings-section

A generator for new sections in AudioBash's React settings screen. React is a library for building user interfaces, and this add-on follows the screen's existing dark, terminal-inspired design.

In plain words
What is it for?
Use it to create toggles, text fields, select menus, and grouped settings with local storage or optional IPC persistence.
Why use it?
It avoids rebuilding common settings controls and styling patterns by hand, reducing the chance that new options look or behave differently from the rest of the screen.

Command for Claude Code

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.

agentmods
npx agentmods add commands/jamditis/audiobash/settings-section
Clone the repo
git clone --depth 1 https://github.com/jamditis/audiobash

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,165 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01165
Opus 5 $0.00000 $0.00583
Sonnet 5 $0.00000 $0.00233
Haiku 4.5 $0.00000 $0.00117

Measured yesterday against content hash e1347362d8fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

settings-section 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 yesterday.

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/commands/settings-section.md · 150 lines

How it starts

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

Settings Section Generator

You are a React developer who maintains AudioBash's Settings.tsx (1,007 lines). Generate UI sections that match the void/brutalist aesthetic perfectly.

Your Expertise

You know the exact patterns used in Settings.tsx:

  • Tailwind classes for the dark theme
  • localStorage + optional IPC persistence
  • Toggle switches, text inputs, selects, and compound sections
  • The section wrapper pattern with labels and descriptions

Color Palette (Memorize These)

Backgrounds: bg-void-100 (#0a0a0a), bg-void-200 (#111111), bg-void-300 (#1a1a1a)
Text: text-crt-white (#f0f0f0), text-crt-white/50, text-crt-white/30
Accent: text-accent (#ff3333), bg-accent
Success: text-crt-green (#33ff33), bg-crt-green
Warning: text-crt-amber (#ffaa00)
Borders: border-void-300, hover:border-crt-white/20

Section Templates

Toggle Switch

{/* Setting Name */}
<div className="space-y-3">
  <div className="flex items-center justify-between">
    <label className="block text-[10px] text-crt-white/50 font-mono uppercase">
      Setting Name
    </label>
    <button
      onClick={() => setEnabled(!enabled)}
      className={`w-10 h-5 rounded-full transition-colors ${
        enabled ? 'bg-crt-green' : 'bg-void-300'
      }`}
    >
      <div className={`w-4 h-4 rounded-full bg-crt-white transition-transform ${
        enabled ? 'translate-x-5' : 'translate-x-0.5'
      }`} />
    </button>
  </div>
  <p className="text-[9px] text-crt-white/30">
    Description of what this setting does.
  </p>
</div>

Text Input

{/* Setting Name */}
<div className="space-y-2">
  <label className="block text-[10px] text-crt-white/50 font-mono uppercase">
    Setting Name
  </label>
  <input
    type="text"
    value={value}
    onChange={(e) => setValue(e.target.value)}
    placeholder="Placeholder text"
    className="w-full bg-void-200 border border-void-300 rounded px-3 py-2 text-sm text-crt-white font-mono placeholder-crt-white/20 focus:outline-none focus:border-accent/50"
  />
  <p className="text-[9px] text-crt-white/30">
    Helper text explaining the input.
  </p>
</div>

Read the full file on GitHub · 150 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. yesterday First seen · 150 lines · 0 tokens per session scan A e1347362d8fa

Subscribe to this mod's changes

settings-section is a command published in the GitHub repository jamditis/audiobash (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,165 tokens. 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.