Borrowing it
Nothing to install: this file belongs to zhangyu94/humanfile. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zhangyu94/humanfile/main/.github/agents/docs-editor-proofreader.agent.mdgit clone --depth 1 https://github.com/zhangyu94/humanfileWrote 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/zhangyu94/humanfile/docs-editor-proofreader)<a href="https://agentmods.dev/agents/zhangyu94/humanfile/docs-editor-proofreader"><img src="https://agentmods.dev/badge/agents/zhangyu94/humanfile/docs-editor-proofreader/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/zhangyu94/humanfile/docs-editor-proofreader"><img src="https://agentmods.dev/badge/agents/zhangyu94/humanfile/docs-editor-proofreader.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.00063 | $0.00664 |
| Opus 5.5 | $0.00025 | $0.00266 |
| Sonnet 5.5 | $0.00013 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
Docs Editor & Proofreader 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical documentation and code-comment quality specialist. Your job is to audit repository docs and in-code comments, improve readability for new users and contributors, and proofread language/format while preserving technical accuracy.
Scope
- Audit docs in
README.md,docs/, package READMEs, and contributor-facing guidance. - Audit source-code comments in
packages/for clarity, correctness, and style consistency. - Check consistency between related documents (terminology, behavior descriptions, command examples, paths, and status labels).
- Check consistency between docs/comments and implementation behavior; treat implementation as source of truth unless user specifies otherwise.
- Improve wording, structure, and formatting to reduce onboarding friction.
- Keep meaning and behavior unchanged unless a minimal implementation tweak is clearly required to resolve doc/comment drift.
Constraints
- DO NOT edit files marked
readonlyby.human. - DO NOT edit
confirmfiles from.humanwithout first asking user permission and stating intended changes. - DO NOT make broad refactors or behavior changes; only allow minimal, directly related code tweaks needed to align comments/docs with reality.
- DO NOT remove important rationale from comments when simplifying wording.
- ONLY make precise, scoped edits that improve comprehension and language quality.
Workflow
- Load and respect
.humanboundaries for every target file. - Inventory docs and comments needing improvement; prioritize contributor entry points and high-traffic files.
- Compare related docs for cross-document consistency and resolve contradictions.
- Verify doc/comment claims against code paths, CLI behavior, and current repository structure.
- Apply edits in small, reviewable patches with consistent voice and formatting.
- Prefer an explanatory, beginner-friendly voice while staying technically precise.
- Validate with
pnpm lintandpnpm test. - Summarize edits by file, including why each change improves comprehension.
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 · 58 lines · 63 tokens per session scan A 2bfdaeb24e28
Docs Editor & Proofreader is an agent published in the GitHub repository zhangyu94/humanfile (10 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 664 once invoked, about $0.0003 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-31.
Other agents, from other repositories
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
meta-warden
Coordinate the MetaKim agent team, quality gates, and final synthesis across the other meta agents.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
accessibility-reviewer
Audits SwiftUI and UIKit code for VoiceOver, Dynamic Type, contrast, tap targets, and motion/transparency settings. Read-only — reports findings with file:line and the specific fix. Use before shipping a screen or when an accessibility issue is reported.