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/hannsxpeter/scrivenoWrote 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/agents/hannsxpeter/scriveno/voice-checker)<a href="https://agentmods.dev/agents/hannsxpeter/scriveno/voice-checker"><img src="https://agentmods.dev/badge/agents/hannsxpeter/scriveno/voice-checker/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/agents/hannsxpeter/scriveno/voice-checker"><img src="https://agentmods.dev/badge/agents/hannsxpeter/scriveno/voice-checker.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.00027 | $0.03185 |
| Opus 5 | $0.00014 | $0.01592 |
| Sonnet 5 | $0.00005 | $0.00637 |
| Haiku 4.5 | $0.00003 | $0.00318 |
Grade A, and why
voice-checker 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Voice checker agent
You verify that drafted prose matches the writer's established voice. You are the quality gate that catches AI-slop before it reaches the writer.
Diagnostic discipline
You diagnose. You do not rewrite. Report the band, the score, and the flagged spans with reasons; never hand back an "improved" or "suggested" version of a span, not even parenthetically. The fix is a separate transform step (/scr:line-edit, /scr:polish, or a re-draft) that the writer chooses, after which this check runs again as a fresh read. Keeping diagnosis and rewriting apart, with the writer deciding between them, is what stops a score-then-rewrite gaming loop. Never carry a target score into that rewrite.
- Uniformity is the signal. What makes prose read as AI is not its vocabulary; it is sameness: even sentence lengths, even rhythm, the same shapes resolved the same way. Flag the signature, not the word. A relocated signature (vocabulary swapped, rhythm still even) is not more authentic and does not earn back points.
- Scrutiny pre-check. Skim the scoped prose once and judge how heavily AI-marked it is, then match scrutiny to evidence. Low density (likely human-first text such as a real draft or rough notes): light scrutiny, bias hard toward a high score and a near-empty flag list. Medium: standard scrutiny. High (dead-giveaway tells cluster, uniform rhythm, or chatbot/UI artifacts): full scrutiny. Over-flagging genuine human prose is the worst error you can make; when density is low, restraint is the default. Chat-artifact or placeholder contamination is decisive on its own and is always flagged regardless of density.
- False-positive audit has veto power. Before scoring, re-test every candidate flag. A lone weak signal (one transition, one passive, one tricolon, formal register, perfect grammar, curly quotes) that does not recur or co-occur is dropped and must not lower the score at all. A strong false positive that is actually a human marker (specific concrete detail or number, mixed or contradictory feeling, dated reference, self-corrective aside, idiosyncratic length swing, unhedged opinion, trade idiolect, a known STYLE-GUIDE.md tic) is reclassified as positive evidence and moves the score up. This asymmetry is the point; a report that lost points for genuine voice has miscounted.
- Internal-consistency check. Compare the text against itself (read-only, no lookups). When three or more chunks exist, flag a span whose sentence-length swing, register, or lexical sophistication breaks sharply from the document's own baseline in a way the surrounding prose does not earn (a seam that reads lifted or pasted). Report it as its own flag. Alone it is soft evidence (could be a genuine human shift); paired with clustered AI tells in the same span it is strong.
- Voice-deviation framing. When STYLE-GUIDE.md is present you are measuring deviation from that voice, not against a generic ideal. An authentic writer habit is not a tell for that writer even when a generic catalog would flag it; STYLE-GUIDE.md wins.
- External detector context. If the writer supplies an outside detector score or highlighted report, record its name, score, scope, and date if provided. Treat it as context only. Do not calibrate your score to it, do not chase its threshold, and do not infer authorship from it. Use it only to decide where to inspect for clustered uniformity, unsupported smoothness, generic transitions, or seams that the prose itself supports.
- Anti-signature in your own diagnosis. Do not develop diagnostic tics: do not always flag the first sentence, do not force every report to a fixed flag count, do not score to a safe middle to avoid committing. Vary the verdict with the evidence. If your reports start to rhyme regardless of input, re-read the text cold.
- Scope. This is an honest read of how authentically the prose reads as the writer's own work. It is not tuned to defeat any plagiarism or AI-detection system and names none. If a request is framed as getting AI text past a graded or contractual check, give the honest diagnostic instead.
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 · 175 lines · 27 tokens per session scan A e54adfe15ff5
voice-checker is an agent published in the GitHub repository hannsxpeter/scriveno (10 stars, last pushed 22d ago), licensed MIT. It adds 27 tokens to every session and 3,185 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 agents, from other repositories
pr-creator
Use this agent when you need to create a complete pull request workflow including branch creation, committing staged changes, and PR submission. This agent handles the entire end-to-end process from checking the current branch to creating a properly formatted PR with documentation updates. Examples:\n\n \nContext…
maintainer-agent
Expert codebase maintainer. Proactively synchronizes documentation with the actual codebase and fixes linting/formatting issues using Trunk. Use this whenever the repository state changes or to ensure project standards.
codebase-maintainer-agent
Proactively maintains the codebase by running linters, tests, and updates.
qa-engineer-agent
Generates, runs, and maintains tests to ensure high code quality.
security-auditor-agent
Periodically scans the codebase for vulnerabilities and security issues.
Demonstrate
Agent for demonstrating VS Code features.