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/paulpreibisch/agentvibes/verbositygit clone --depth 1 https://github.com/paulpreibisch/AgentVibesWrote 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/paulpreibisch/agentvibes/verbosity)<a href="https://agentmods.dev/commands/paulpreibisch/agentvibes/verbosity"><img src="https://agentmods.dev/badge/commands/paulpreibisch/agentvibes/verbosity.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.1 | $0.00017 | $0.00772 |
| Opus 5 | $0.00009 | $0.00386 |
| Sonnet 5 | $0.00003 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
verbosity 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get or set the AgentVibes verbosity level to control how much Claude speaks while working.
Usage
/agent-vibes:verbosity- Show current verbosity level/agent-vibes:verbosity low- Set to LOW (minimal)/agent-vibes:verbosity medium- Set to MEDIUM (balanced)/agent-vibes:verbosity high- Set to HIGH (maximum transparency)/agent-vibes:verbosity caveman- Set to CAVEMAN (ultra-terse, max token savings)
Verbosity Levels
LOW (Minimal)
- ✅ Acknowledgments only (start of task)
- ✅ Completions only (end of task)
- 🔇 No reasoning spoken during work
- Perfect for: Quiet work sessions, minimal distraction
MEDIUM (Balanced)
- ✅ Acknowledgments
- 🤔 Major decisions ("I'll use grep to search")
- ✓ Key findings ("Found 12 instances")
- ✅ Completions
- Perfect for: Understanding major decisions without full narration
HIGH (Maximum Transparency)
- ✅ Acknowledgments
- 💭 All reasoning ("Let me search for all instances")
- 🤔 All decisions ("I'll use grep for this")
- ✓ All findings ("Found it at line 1323")
- ✅ Completions
- Perfect for: Full transparency, learning mode, debugging complex tasks
CAVEMAN (Ultra-Terse)
- ⚡ Fragments only — no articles, filler, or hedging
- 🔤 Abbreviations (DB/auth/config/fn/impl)
- ➡️ Arrows instead of prose (X -> Y)
- 📉 65-75% fewer output tokens
- Perfect for: Maximum token savings, cost-conscious sessions
- Inspired by caveman (MIT)
How It Works
Claude uses emoji markers in its reasoning text:
- 💭 = Reasoning/thinking
- 🤔 = Decisions
- ✓ = Findings/results
Based on your verbosity level, AgentVibes automatically detects these markers and speaks them aloud.
Examples
LOW Verbosity
User: "Find all TODO comments"
[TTS: "I'll search for those"]
[Work happens silently...]
[TTS: "Found 12 TODO comments"]
MEDIUM Verbosity
User: "Find all TODO comments"
[TTS: "I'll search for those"]
🤔 I'll use grep to search all files
[Work happens...]
✓ Found 12 TODO comments across 5 files
[TTS: "Found 12 TODO comments"]
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.
- 2d ago First seen · 99 lines · 17 tokens per session scan A d56647186ce6
verbosity is a command published in the GitHub repository paulpreibisch/AgentVibes (153 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 772 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-09-03.
Other commands, from other repositories
email-domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
email-providers
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
open
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
whoami
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
workflow-manager
Process automation with TodoWrite planning and Task execution.
t_metaprompt_workflow
Based on the High Level Prompt follow the Workflow, to create a new prompt in the Specified Format. Before you start, WebFetch everything in the Documentation.