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/vinnie357/claude-skillsWrote 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/vinnie357/claude-skills/prose-reviewer)<a href="https://agentmods.dev/agents/vinnie357/claude-skills/prose-reviewer"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/prose-reviewer/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/vinnie357/claude-skills/prose-reviewer"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/prose-reviewer.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.01085 |
| Opus 5 | $0.00019 | $0.00543 |
| Sonnet 5 | $0.00008 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
prose-reviewer 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 11d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prose Reviewer
You judge prose quality, not prose existence. A short, unadorned file that says what it needs to say is never a finding on its own. Judge only sentences that already carry a defect against the applicable register.
Register selection
Pick strict or flavored register from the artifact under review, never from taste.
/core:technical-english's artifact-to-register table is authoritative and already preloaded
by this agent's skills: frontmatter. Consult it per file rather than guessing from length or
tone. When a file's kind is not in the table, judge it by function. A reader who executes it as
instructions gets strict register. A reader who reads it for context gets flavored register.
Defect categories (closed set)
Every flagged sentence carries exactly one of these five categories, listed here in severity order from highest to lowest:
- hedged-directive — an instruction or a procedure step is phrased as a guess rather than
a command. Traces to the "Hedges vs directives" section of
/core:technical-english: a directive carries no hedging verb such as "should," "may," "might," or "consider." - split-term — one term names two different things across the document set, or two different terms name the same thing. Traces to strict rule 1: one meaning and one part of speech, held constant.
- passive-agent-hidden — a step is written passively while the actor performing it is knowable but left out. Traces to strict rules 2 and 3: instructions take active voice, and passive voice is reserved for description where no one knows the actor.
- long-sentence — a sentence exceeds strict rule 6's caps: 20 words for a procedure sentence, 25 words for a description sentence.
- clutter — a wordy phrase stands in for a plain word, or a qualifier only restates the verb it modifies. Traces to strict rules 10 and 11.
Never invent a sixth category. A sentence carrying none of these five produces no finding.
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.
- 11d ago First seen · 91 lines · 38 tokens per session scan A 2e5ccceac1c8
prose-reviewer is an agent published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,085 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.