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 solo-super/marketplace --skill voice-editorgit clone --depth 1 https://github.com/solo-super/marketplaceWrote 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/solo-super/marketplace/voice-editor)<a href="https://agentmods.dev/skills/solo-super/marketplace/voice-editor"><img src="https://agentmods.dev/badge/skills/solo-super/marketplace/voice-editor/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/solo-super/marketplace/voice-editor"><img src="https://agentmods.dev/badge/skills/solo-super/marketplace/voice-editor.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.00038 | $0.03292 |
| Opus 5 | $0.00019 | $0.01646 |
| Sonnet 5 | $0.00008 | $0.00658 |
| Haiku 4.5 | $0.00004 | $0.00329 |
Grade A, and why
voice-editor 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 10d 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 — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Voice doesn't live in first drafts—it lives in editing choices. This skill guides the editing process that turns AI's generic output into something distinctively yours.
<quick_start> Provide:
- Content to edit (paste or file path)
- VOICE.md location (default:
~/.claude/voice/VOICE.md; create one with/voice-analyzer)
The skill will:
- Run slop detection on the content
- Identify voice mismatches against your profile
- Perform multi-pass editing (Structure → Voice → Polish)
- Output edited content with change annotations
- Suggest VOICE.md updates based on patterns found </quick_start>
<the_editing_reality> The 30-40% Rule:
Even with a perfect style guide, expect to edit 30-40% of AI output to make it distinctively yours. This isn't a problem—it's the feature.
30-40% editing effort is dramatically less than 100% writing-from-scratch effort, while producing work that sounds more like you than unguided AI ever could.
If you're editing more than 50%: Your style guide needs refinement, or your prompts need work.
If you're editing less than 20%: You might be accepting too much generic content. </the_editing_reality>
<editing_workflow> Focus: Does the organization serve the content?
Opening Mechanics (from writing-quality):
- Does opening create a SPECIFIC question? Not vague mystery - readers need enough context to form a particular question they want answered
- Does first paragraph contain change or threat of change? Brains notice disruption of status quo
- Is first paragraph under 50 words / 3 sentences?
- First line hits 3+ of: question, character, setting, tone, movement?
Questions to ask:
- Does the opening hook or just clear throat?
- Is there a clear progression of ideas?
- Does each section earn its place?
- Is anything redundant or missing?
- Does the conclusion land or just stop?
Scene/Section Structure:
- Does each section follow Goal → Conflict → Outcome?
- Are transitions connected by "because" not "and then"?
- Are characters/subjects in motion during slow passages?
Actions:
- Cut throat-clearing openings ("In this article, we'll explore...")
- Reorder sections for better flow
- Merge redundant sections
- Add missing transitions
- Strengthen weak conclusions
- Add change to opening if missing - start with what changed, not background
- Make question specific - "Why is the other side of the bed cold?" not "Something is happening"
Check against VOICE.md:
- Sentence length patterns (matching variance?)
- Vocabulary fingerprint (right formality level?)
- Tone markers (humor, directness, reader relationship?)
- Structural habits (lists vs prose, formatting?)
- Opinion expression (appropriate confidence level?)
Actions:
- Replace formal language with conversational equivalents
- Vary sentence lengths to match profile
- Add characteristic phrases from the voice profile
- Adjust opinion strength to match profile
- Fix paragraph rhythm
Scan for:
- Tier 1 phrases (remove immediately)
- Tier 2 patterns (check context)
- Tier 3 clusters (break up if grouped)
- Structural tells (uniformity, over-balance)
- Staccato fragment spam (3+ consecutive short declarative sentences)
- Comparator sentences ("This isn't X. It's Y." patterns)
Actions:
- Delete or replace all Tier 1 phrases
- Evaluate Tier 2 in context, remove if generic
- Redistribute Tier 3 to avoid clustering
- Vary sentence lengths if too uniform
- Rebalance sections if all equal weight
- Combine staccato fragments into flowing prose with commas, em-dashes, or conjunctions
- Rewrite comparators directly — just say what something IS, don't waste words on what it isn't
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.
- 10d ago First seen · 398 lines · 38 tokens per session scan A 9cbb2e9f4281
voice-editor is a skill published in the GitHub repository solo-super/marketplace (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 3,292 once invoked, about $0.0002 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…