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.
npx agentmods add commands/chalyx/claude-bell/volumegit clone --depth 1 https://github.com/ChALyX/claude-bellWrote 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.
[](https://agentmods.dev/commands/chalyx/claude-bell/volume)<a href="https://agentmods.dev/commands/chalyx/claude-bell/volume"><img src="https://agentmods.dev/badge/commands/chalyx/claude-bell/volume.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00015 | $0.00234 |
| Opus 5 | $0.00008 | $0.00117 |
| Sonnet 5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
volume 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 3d 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.
What it actually says
The user wants to set the claude-bell notification sound volume to: $ARGUMENTS
Follow these steps:
- Validate that the argument is an integer between 0 and 100. If it is empty or invalid, read
~/.claude/claude-bell/volume.txtand report the current volume (default 100 if the file does not exist), show the usage/claude-bell:volume <0-100>, then stop. - Ensure the directory
~/.claude/claude-bell/exists, then write the integer to~/.claude/claude-bell/volume.txt(the number only, nothing else). - Play a test sound at the new volume so the user can confirm:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/play-sound.sh" complete - Tell the user: volume is set to N, effective immediately (read on every playback, no restart needed); 0 means mute.
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.
- 3d ago First seen · 14 lines · 15 tokens per session scan A 1c85b62dcf67
volume is a command published in the GitHub repository ChALyX/claude-bell (1 stars, last pushed 18d ago), licensed MIT. It adds 15 tokens to every session and 234 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.
Other commands, from other repositories
coach
Coaching analysis command. Performs data-driven work-pattern analysis and offers personal improvement suggestions.
content-close
Content session close command. Summarizes the day's output, prepares for tomorrow, and notes learnings.
sc-detail
Throughline の退避済みターン（L2 本文 + L3 ツール入出力）を時刻で復元する.
brief
Open/focus the docked pane showing this session's live summary brief.
tl
Throughline の UserPromptSubmit hook が /tl を検出し、バトン（現セッション ID）を保存しました。.
voice-mute
Time-bound mute for both voice + notifications (default 30m). --global for user scope.