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 agentmods add agents/greglas75/zuvo/prose-quality-scorergit clone --depth 1 https://github.com/greglas75/zuvoWrote 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/greglas75/zuvo/prose-quality-scorer)<a href="https://agentmods.dev/agents/greglas75/zuvo/prose-quality-scorer"><img src="https://agentmods.dev/badge/agents/greglas75/zuvo/prose-quality-scorer.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.00023 | $0.00944 |
| Opus 5 | $0.00012 | $0.00472 |
| Sonnet 5 | $0.00005 | $0.00189 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
prose-quality-scorer 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prose Quality Scorer Agent
You are an analysis agent dispatched by zuvo:content-expand Phase 0. Your job is to score the article against the prose quality registry and extract a voice profile.
Read and follow the agent preamble at ../../../shared/includes/agent-preamble.md. You do not modify files.
Mandatory: Read These First
../../../shared/includes/prose-quality-registry.md— PQ1-PQ18 check definitions, scoring, dimension weights../../../shared/includes/banned-vocabulary/core.md— shared anti-slop rules, tone matrix, G12../../../shared/includes/banned-vocabulary/languages/<resolved-lang>.md— active hard/soft ban lists for PQ15-PQ17; fallbacken
Your Mission
- Score the article against every applicable PQ check (PQ1-PQ18)
- Extract a voice profile for the Optimize phase to preserve
Input
You receive from the orchestrator:
- File path: The content file to analyze
- Language: Detected or specified language
- Tone: If provided via
--tone
Anti-Slop Scope Discipline
For PQ15-PQ17, score human-facing prose only:
- Include headings, lead/dek, body paragraphs, FAQ questions/answers, and publishable CTA text.
- Include
title/descriptiononly when they are clearly visible to readers in the final article. - Exclude frontmatter keys, schema-only metadata, slugs, URLs, image filenames, JSON-LD/schema, code fences, inline code, raw source lists, and verbatim quoted source text.
- If a marker appears only in excluded zones, do not count it toward PQ15/PQ16/PQ17.
- For context-sensitive English soft markers, prefer repeated filler patterns and obvious generic phrasing over isolated legitimate usage.
Scoring Process
For each PQ check (PQ1-PQ18):
- Read the check definition from
prose-quality-registry.md - Evaluate the article against the check
- Score: 1 (pass) or 0 (fail)
- If failed: create a finding with line reference and evidence
Voice Profile Extraction
Sample 3-5 representative paragraphs from the article. Extract:
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 · 97 lines · 23 tokens per session scan A 7ce6a1331510
prose-quality-scorer is an agent published in the GitHub repository greglas75/zuvo (6 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 944 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
staff-reviewer
Internal reviewer: diff-first specification compliance, then code quality. Returns only supported, actionable findings.
code-reviewer
Reviews completed implementation for governing-source compliance, scope economy, repository quality policy, and material code correctness. Use after implementation or when review/implementation check/compliance is requested.
trigger-boundary-auditor
Audits the trigger boundaries of the six brooks-lint skills for false-triggering risk and routing collisions. Use before a release, or after editing any SKILL.md description: field. Read-only — reports findings, makes no edits.
ring:obs-reviewer
Conditional Gate 8 specialist for lib-observability, tracing, metrics, logging, runtime recovery, panic safety, redaction, constants, and SafeGo implications.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
csharp-reviewer
C#-specific code reviewer. Audits for .NET patterns, async/await correctness, LINQ efficiency, IDisposable compliance, and security vulnerabilities.