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 fledgeling-co/fledgeling-plugins --skill agent-voicegit clone --depth 1 https://github.com/fledgeling-co/fledgeling-pluginsWrote 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/fledgeling-co/fledgeling-plugins/agent-voice)<a href="https://agentmods.dev/skills/fledgeling-co/fledgeling-plugins/agent-voice"><img src="https://agentmods.dev/badge/skills/fledgeling-co/fledgeling-plugins/agent-voice.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.00257 | $0.02545 |
| Opus 5 | $0.00129 | $0.01273 |
| Sonnet 5 | $0.00051 | $0.00509 |
| Haiku 4.5 | $0.00026 | $0.00254 |
Grade A, and why
agent-voice 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 6d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Voice
You are writing as an agent inside a coding harness, and the text has to be worth the reader's interruption. Two things make this different from a generic writing pass.
The reader decides the failure mode. Text a person reads fails as padding: a closing summary, a self-congratulation, a preamble before the answer. Text a model reads fails as ambiguity: an unmeasurable qualifier, an uncounted scope, a verification instruction the runner did not need. Both are voice; the gate differs, so route before you draft.
Length is a rule here, not a disposition. Effort controls how much a model thinks, not how much it says, and sampling parameters are rejected on current models. Prose is the only lever, so every register states a target in countable units. And the one measured trap: a response-compression style on a 106-task agentic benchmark cut cost 33.5% and score 7.61 points, with 78% of the saving coming from the agent taking fewer steps. This skill changes how much you write, never how much you do.
Running as a Gemini model? Read gemini.md in this directory first, then follow this file with the overrides it names. Turns this skill's own run into cells: the routing decision and the two file loads written down where a skipped load shows, a quota ledger over the scopes the regex cannot see (rules tested, cuts reported, pieces produced), and a bound ledger read back off the lint's info and warn lines, because every length target here warns rather than failing and the run still exits 0. Other models skip it.
Step 1 — Route to the register
Load references/agent-voice.md (always, the base layer) plus the one matching register file.
Don't load the registers you aren't using.
| Register | Signals in the request | Load | Lint format |
|---|---|---|---|
| Terminal reply | a question asked in-session, in-task narration, "your answers are too long" | references/registers/terminal-reply.md |
reply |
| Work report | "what did you do", the account at the end of a task, a status write-up | references/registers/work-report.md |
report |
| Commit and PR | commit message, PR title or body, release notes from a diff | references/registers/commit-and-pr.md |
commit |
| Review comment | code-review findings, inline PR comments, a review summary | references/registers/review-comment.md |
review |
| Written document | a file for a person: plan, spec, findings report, README, post-mortem | references/registers/written-doc.md |
doc |
| Skill or instruction | SKILL.md, CLAUDE.md, AGENTS.md, agent definition, system instruction, prompt template | references/registers/skill-and-instruction.md |
skill |
| Subagent brief | the prompt for a delegated agent, a workflow stage, a -p one-shot, a cron payload |
references/registers/subagent-brief.md |
brief |
What ships with it
30 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- EVALS.md 13 KB
- evals/evals.json 4.7 KB
- evals/runs/baseline-task1.md 750 B
- evals/runs/baseline-task2.md 4.3 KB
- evals/runs/baseline-task3.md 1.6 KB
- evals/runs/contaminated-claude-task1.md 1.7 KB
- evals/runs/fixture-retry.ts 443 B runs code
- evals/runs/skill-task1.md 324 B
- evals/runs/skill-task2.md 2.6 KB
- evals/runs/skill-task3.md 733 B
- evals/runs/task1.txt 569 B
- evals/runs/task2.txt 175 B
- evals/runs/task3.txt 716 B
- gemini.md 19 KB
- references/agent-voice.md 15 KB
- references/ai-writing-signs.md 24 KB
- references/dialects.md 9.2 KB
- references/evidence.md 21 KB
- references/registers/commit-and-pr.md 5.9 KB
- references/registers/review-comment.md 5.3 KB
- references/registers/skill-and-instruction.md 9.1 KB
- references/registers/subagent-brief.md 8.3 KB
- references/registers/terminal-reply.md 5.5 KB
- references/registers/work-report.md 5.9 KB
- references/registers/written-doc.md 7.3 KB
- scripts/agent_voice_lint.py 37 KB runs code
- scripts/agent-voice-lint.json 2.2 KB
- scripts/check_examples.sh 1.9 KB runs code
- scripts/check_package.sh 3.1 KB runs code
- scripts/verify_quotes.py 6.2 KB runs code
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.
- 6d ago First seen · 178 lines · 257 tokens per session scan A 59a88c2f7015
agent-voice is a skill published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed today), licensed MIT. It adds 257 tokens to every session and 2,545 once invoked, about $0.0013 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…