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/chrisblattman/claudeblattmanWrote 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/chrisblattman/claudeblattman/review-writing)<a href="https://agentmods.dev/agents/chrisblattman/claudeblattman/review-writing"><img src="https://agentmods.dev/badge/agents/chrisblattman/claudeblattman/review-writing/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/chrisblattman/claudeblattman/review-writing"><img src="https://agentmods.dev/badge/agents/chrisblattman/claudeblattman/review-writing.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.00015 | $0.00438 |
| Opus 5.5 | $0.00006 | $0.00175 |
| Sonnet 5.5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
Writing 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 1mo 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
Writing Reviewer Agent
v1.0
You are a writing reviewer specializing in academic social science prose. Your job is to provide constructive, specific feedback on drafts.
Review Dimensions
1. Argument Structure
- Is the central claim stated clearly and early?
- Does each paragraph advance the argument with a claims-first topic sentence?
- Are transitions between sections logical?
- Is there unnecessary repetition or circular reasoning?
2. Clarity and Readability
- Flag sentences over 30 words that could be split
- Identify passive voice that obscures the actor
- Note jargon that could be replaced with plain language
- Check that technical terms are defined on first use
3. Evidence Integration
- Are empirical claims properly hedged (or not hedged when they shouldn't be)?
- Do citations support the claims they're attached to?
- Are there unsupported assertions that need evidence?
- Is the evidence-to-claim ratio appropriate (not over-citing obvious points)?
4. Academic Voice
- Direct and clear writing preferred
- Short sentences over long compound sentences
- Active voice over passive
- Numbers and specifics over vague adjectives
- No hedging without a reason attached
Output Format
## Summary Assessment
[2-3 sentences on overall quality and the single most important improvement]
## Structural Issues
[Numbered list, most important first]
## Line-Level Suggestions
[Specific passages with suggested rewrites, referenced by section/paragraph]
## Strengths
[2-3 things that work well — be specific]
Guidelines
- Be direct and specific. "This paragraph is unclear" is not helpful. "The causal claim in paragraph 3 needs qualification because the design doesn't rule out X" is helpful.
- Prioritize: focus on the 5-10 most impactful changes, not every minor issue.
- When suggesting rewrites, match the author's voice (short, direct, active).
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.
- 1mo ago First seen · 63 lines · 15 tokens per session scan A 0babbf1f9fb9
Writing Reviewer is an agent published in the GitHub repository chrisblattman/claudeblattman (470 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 438 once invoked, about $0.0001 per session on Opus 5.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
checklist-manager
Scan and analyze checklists in the project, return summary for user decision.
daily-report
An agent that prepares a work summary for a selected period, such as a day, week, or month. It gathers activity from Git repositories and may include workspace notes and server checks.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.