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-refreshgit 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-refresh)<a href="https://agentmods.dev/skills/solo-super/marketplace/voice-refresh"><img src="https://agentmods.dev/badge/skills/solo-super/marketplace/voice-refresh/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-refresh"><img src="https://agentmods.dev/badge/skills/solo-super/marketplace/voice-refresh.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.00036 | $0.02231 |
| Opus 5 | $0.00018 | $0.01115 |
| Sonnet 5 | $0.00007 | $0.00446 |
| Haiku 4.5 | $0.00004 | $0.00223 |
Grade A, and why
voice-refresh 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 9d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Style guides aren't static. Your voice evolves. When the guide doesn't evolve with you, it becomes a constraint instead of a tool—you start rewriting 60-70% of content instead of the expected 30-40%.
<quick_start> Monthly check (15 min):
/voice-refresh monthly
- Reviews 3 recent pieces
- Checks if they still sound like you
- Suggests minor updates
Quarterly overhaul (1 hour):
/voice-refresh quarterly [new samples]
- Analyzes new writing samples
- Compares to existing VOICE.md
- Identifies evolved patterns
- Generates updated guide
Problem-driven refresh:
/voice-refresh diagnose [problematic content]
- Analyzes why content feels off
- Identifies guide gaps
- Suggests specific fixes </quick_start>
<warning_signs> Your guide needs refreshing when:
- AI output consistently feels "off" even with the guide
- You're rewriting more than 50% of AI content
- Your natural writing doesn't match the guide anymore
- You've developed new phrases or patterns AI doesn't know
- You're avoiding topics because the guide doesn't handle them
- Voice starts strong but drifts by the end of long pieces
- Readers comment that recent work "doesn't sound like you" </warning_signs>
<monthly_check_process> Pull 3 pieces you've written in the last month using the style guide. Ideally:
- One that felt right
- One that required heavy editing
- One you're unsure about
<quarterly_overhaul_process> Collect 3-5 new writing samples from the past quarter that feel distinctly "you." These should be:
- Written recently (last 3 months)
- Pieces you're proud of
- Representative of your current voice (not historical)
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.
- 9d ago First seen · 324 lines · 36 tokens per session scan A 246b16ebb1cc
voice-refresh is a skill published in the GitHub repository solo-super/marketplace (2 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 2,231 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…