agentmods.dev

configure-bells-and-whistles

configure-bells-and-whistles is a command for Claude Code from etr/bells-and-whistles. It costs 9 tokens per session (1,340 once invoked), scanned B, original, MIT.

An interactive setup command for choosing how Claude Code notifications sound and whether they include voice.

In plain words
What is it for?
Use it to choose sound, voice, or both, and select a theme such as beeps, chirps, videogame, anime, or classical music.
Why use it?
It gathers the notification preferences in one setup flow instead of requiring manual configuration.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the bells-and-whistles plugin — 3 commands, 2 hooks shipped together

not rated 7repo 5mo ago B scan 9 tokens original MIT

Good fit Use it to choose sound, voice, or both, and select a theme such as beeps, chirps, videogame, anime, or classical music.

Compare 6 commands from other repositories ↓
View source ↗ etr/bells-and-whistles
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add etr/bells-and-whistles
Claude Code
/plugin install bells-and-whistles

Made for: Claude Code.

Or install bells-and-whistles, the plugin that ships this one along with the rest of its 3 commands, 2 hooks.

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 configure-bells-and-whistles

README.md
[![agentmods](https://agentmods.dev/badge/commands/etr/bells-and-whistles/configure-bells-and-whistles/github.svg)](https://agentmods.dev/commands/etr/bells-and-whistles/configure-bells-and-whistles)
Your own site
<a href="https://agentmods.dev/commands/etr/bells-and-whistles/configure-bells-and-whistles"><img src="https://agentmods.dev/badge/commands/etr/bells-and-whistles/configure-bells-and-whistles/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 configure-bells-and-whistles

Your own site · 80×15
<a href="https://agentmods.dev/commands/etr/bells-and-whistles/configure-bells-and-whistles"><img src="https://agentmods.dev/badge/commands/etr/bells-and-whistles/configure-bells-and-whistles.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 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,340 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00009 $0.01340
Opus 5 $0.00005 $0.00670
Sonnet 5 $0.00002 $0.00268
Haiku 4.5 $0.00001 $0.00134

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

Security

Grade B, and why

configure-bells-and-whistles scanned grade B with 1 finding 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 12d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Read `~/.claude/settings.json`. If it contains hook entries under `Stop` or `Notification` that reference `~/.claude/hooks/notify-sound.sh`, remove those specific entries (but preserve any other hooks and all other setti
commands/configure-bells-and-whistles.md · 132 lines

How it starts

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

You are the bells-and-whistles installer. Guide the user through configuring notification sounds for Claude Code.

Steps

1. Ask notification mode

Use AskUserQuestion to ask:

  • Question: "How should bells-and-whistles notify you?"
  • Options: ["Sound + Voice", "Sound only", "Voice only"]

Map the response:

  • "Sound + Voice" → sound_and_voice
  • "Sound only" → sound_only
  • "Voice only" → voice_only

2. Ask theme

Use AskUserQuestion:

  • Question: "Pick a notification sound theme:"
  • Options: ["Videogame", "Disney Adults", "Anime", "Movie Addicts", "90s Rock", "Classical Music", "Beeps/Tones", "Chirps", "Cyberpunk 2077", "D&D / Fantasy"]

Map:

  • "Videogame" → videogame
  • "Disney Adults" → disney
  • "Anime" → anime
  • "Movie Addicts" → movies
  • "90s Rock" → 90s_rock
  • "Classical Music" → classical
  • "Beeps/Tones" → beeps
  • "Chirps" → chirps
  • "Cyberpunk 2077" → cyberpunk
  • "D&D / Fantasy" → dnd

3. Check for themed phrases (if voice enabled)

If the mode includes voice (sound_and_voice or voice_only):

Read ${CLAUDE_PLUGIN_ROOT}/speech_phrases.json. Check if the selected theme has its own entry (i.e., a key other than "default" matching the theme name).

If the theme has custom phrases, use AskUserQuestion:

  • Question: "The [theme] theme has custom themed phrases (e.g., '[first stop phrase from the theme]'). Use themed phrases or standard ones?"
  • Options: ["Themed phrases", "Standard phrases"]

Set use_themed_phrases:

  • "Themed phrases" → true
  • "Standard phrases" → false

If the theme does NOT have custom phrases, set use_themed_phrases to false.

If mode is sound_only, set use_themed_phrases to false.

4. Ask accent and gender (if voice enabled AND NOT using themed phrases)

If the mode includes voice (sound_and_voice or voice_only) AND use_themed_phrases is false:

Use AskUserQuestion to ask accent:

  • Question: "Which accent?"
  • Options: ["US English", "UK English"]

Map: "US English" → us, "UK English" → uk

Read the full file on GitHub · 132 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. 12d ago First seen · 132 lines · 9 tokens per session scan B aa70f7deeaa7

Subscribe to this mod's changes

configure-bells-and-whistles is a command published in the GitHub repository etr/bells-and-whistles (7 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 1,340 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens