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.
git clone --depth 1 https://github.com/stepolan/marketing-repo-templateWrote 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/stepolan/marketing-repo-template/voice-check)<a href="https://agentmods.dev/commands/stepolan/marketing-repo-template/voice-check"><img src="https://agentmods.dev/badge/commands/stepolan/marketing-repo-template/voice-check/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/commands/stepolan/marketing-repo-template/voice-check"><img src="https://agentmods.dev/badge/commands/stepolan/marketing-repo-template/voice-check.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.00011 | $0.00440 |
| Opus 5 | $0.00005 | $0.00220 |
| Sonnet 5 | $0.00002 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
voice-check 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 12d 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
Run a voice consistency check on the specified draft file.
Target file: $ARGUMENTS
-
Read the target draft file. If no file specified, ask which file to check.
-
Load the voice profile:
- Read the relevant author's voice profile at
/authors/<name>/voice/voice-profile.md - Read
/brand/voice-guidelines.md
- Read the relevant author's voice profile at
-
Check the draft against voice patterns. Flag:
- Contractions used (don't, won't, it's, etc.) — should be written out
- Em dashes (—) or double hyphens (--) used — should use periods or colons
- Single space after punctuation — should be two spaces
- Passive voice — should be active
- Preachy or teaching tone toward peers
- Blame language toward engineers/teams
- Corporate jargon (synergy, leverage, best-in-class)
- Hype language (game-changing, revolutionary)
- Lead is buried — most interesting insight not in first 3 sentences
- Credentials listed in body (titles, companies, years)
- Engagement bait closing ("Agree?" "Thoughts?")
- Single-line poetry formatting (blog should be paragraphs, LinkedIn should be 2-3 sentence paragraphs)
- Correct title used per
brand/author-bios.md
-
Report results:
## Voice Check Results — [filename] ### PASS - [Rule]: [Brief confirmation] ### FAIL - [Rule] (line N): `[offending text]` → `[suggested fix]` ### Overall: [Strong / Needs Work / Off Voice]Every FAIL item must include a specific line number and a before/after suggestion.
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.
- 12d ago First seen · 48 lines · 11 tokens per session scan A b8b48ea81ca0
voice-check is a command published in the GitHub repository stepolan/marketing-repo-template (2 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 440 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-08-31.
Other commands, from other repositories
repurpose
Fan a QA'd long-form piece (blog, research, weekly report) down into 6 channel-native formats — X thread, X singles, LinkedIn article, newsletter snippet, and pull-quote cards. Every output is canon-checked and staged for review.
blog-assets
Build HTML templates for each visual placeholder in a blog article and batch-export them as 1200x675 PNGs at 2x. Fourth step in the blog production pipeline.
blog-pipeline
Reference document showing the full Blog Engine flow with human approval gates. This is not an executable command — it's a map of how blog commands connect.
compliance-check
Jurisdiction-aware content compliance validation. Scans copy for regulatory violations, banned claims, missing disclaimers, and financial promotion language.
blog-publish
Push a completed blog article to the CMS -- upload images, create CMS item, sync components. Final step in the blog production pipeline.
blog-qa
Run the full quality pipeline on a blog draft. Chains /content-qa + /stop-slop + blog-specific checks. Returns READY or NOT READY. Third step in the blog production pipeline.