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 skills add yeisonrestrepo/code-conductor --skill verbositygit clone --depth 1 https://github.com/yeisonrestrepo/code-conductorWrote 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/skills/yeisonrestrepo/code-conductor/verbosity)<a href="https://agentmods.dev/skills/yeisonrestrepo/code-conductor/verbosity"><img src="https://agentmods.dev/badge/skills/yeisonrestrepo/code-conductor/verbosity/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.
<a href="https://agentmods.dev/skills/yeisonrestrepo/code-conductor/verbosity"><img src="https://agentmods.dev/badge/skills/yeisonrestrepo/code-conductor/verbosity.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.00485 |
| Opus 5.5 | $0.00013 | $0.00194 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
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 4d 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
Verbosity
Read ~/.claude/memory/verbosity.md once at the start of every session. Extract the value after VERBOSITY:. Default to MIN if the file is absent or the value is unrecognized.
Levels
MIN (default)
- One declarative sentence per response.
[CHANGES]tag: list of files modified only. No prose explanation unless the user asks.- On failure or ambiguity: one clarifying question. Nothing else.
INFO
- Bullet list: what changed and why. Max 5 bullets.
- Tags:
[CHANGES]+[REASON]. - No prose paragraphs.
VERBOSE
- Full explanation. Prose allowed.
- All applicable tags:
[CHANGES],[REASON],[PLAN],[BUG]. - No length limit.
Application
The active level is enforced by a UserPromptSubmit hook (verbosity-remind.sh) that fires before every response and injects a compact, level-aware reminder into the conversation context. The reminder is injected at each prompt boundary so the constraint survives context fills and session drift — not only at session start.
Read ~/.claude/memory/verbosity.md for the configured level. Default: MIN if the file is absent, unreadable, or contains no valid VERBOSITY: token. To change the level, re-run the installer with --verbosity MIN|INFO|VERBOSE or edit the file directly.
Changes to verbosity.md take effect on the next user prompt — no session restart required. If you edit the file during an active Claude session, the hook picks up the new level on the immediately following prompt; there is no stale session state to clear. If the hook emits at an unexpected level after a change, verify the file was saved (not merely modified in an unsaved buffer), confirm that $HOME resolves to the expected path in the terminal that launched Claude, and check that no parent environment is setting CC_VERBOSITY_SKIP=1.
VERBOSITY_HOOK_VERSION: 1.11.0
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.
- 4d ago First seen · 37 lines · 32 tokens per session scan A 7fddce8cf08a
verbosity is a skill published in the GitHub repository yeisonrestrepo/code-conductor (7 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 485 once invoked, about $0.0001 per session on Opus 5.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-23.
Other skills, from other repositories
digest
Restructure a rambling ticket, email, pasted note, file, or Jira issue - prose the user received - into the fixed digest brief (TL;DR, Next action, Breakdown, Priority). Trigger on an explicit /squirrel:digest invocation, or an explicit request to digest or restructure a named piece of prose into that brief. An…
session-audit
Audit Claude Code session logs (/.claude/projects) for token waste and produce a ranked, attributed efficiency report (habit / skillfile / config). Use when the user asks to audit session efficiency, analyze token waste or cost blowups, review Claude Code usage cost, or asks "where are my tokens going".
create-cmd-instruct
Reshape my PREVIOUS message using extra instructions, then save it as a slash command.
status
Use this skill when the user asks "where am I", "what's the current task", "what's blocking me", "show status", "what needs sign-off", or "what's next". Prints a snapshot of the active plan, gate, sign-off progress, and next action. Reads only — writes nothing.
list-cmds
List all my custom slash commands with their descriptions. Use when the user wants to see, browse, or review the custom slash commands they have saved.
whats-next
Suggest what to work on next based on recent activity and current context. Use when the user is between tasks, at a decision point, wants direction on where to focus, or asks what to do next.