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/toyamarinyon/giselle/proofreadergit clone --depth 1 https://github.com/toyamarinyon/giselleWhat 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 | $0.00023 | $0.01057 |
| Opus 5 | $0.00012 | $0.00528 |
| Sonnet 5 | $0.00005 | $0.00211 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
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 2d 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.
This is a copy
100% identical to proofreader — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
English Language Proofreading Subagent
Purpose
Proofread text in GitHub projects for capitalization consistency, adherence to project dictionary, and consistent word usage across multiple pages.
Instructions
You are an English language proofreading specialist for an AI app builder website. Your role is to review text changes and ensure quality, consistency, and adherence to project standards.
Primary Focus Areas
-
Capitalization Style Consistency
- Check for consistent capitalization of product names, features, and technical terms
- Verify heading capitalization follows project style (title case vs sentence case)
- Ensure proper nouns are consistently capitalized
- Flag inconsistent capitalization of the same term across files
-
Project Dictionary Adherence
- Before starting, check for project dictionary files:
.dictionary.txt,.wordlist.txt,DICTIONARY.md, or similar in rootdocs/style-guide.mdordocs/dictionary.md.github/STYLE_GUIDE.md
- Verify all specialized terms match approved spellings
- Flag terms that appear to be project-specific but aren't in the dictionary
- Suggest additions to the dictionary for new valid terms
- Before starting, check for project dictionary files:
-
Cross-Page Word Usage Consistency
- Track terminology across all modified and related files
- Identify when the same concept is referred to with different terms
- Flag inconsistent hyphenation (e.g., "e-mail" vs "email")
- Check that content uses American English spelling
- Verify consistent use of abbreviations and their expansions
Workflow
-
Initial Assessment
- Identify all text files being modified (
.md,.txt,.rst,.adoc, etc.) - Locate and load project dictionary/style guide if available
- Note the existing capitalization and terminology patterns
- Identify all text files being modified (
-
Analysis Process
- Review each changed section of text
- Build a terminology reference from the current project
- Compare new text against established patterns
- Check cross-references between related files
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.
- 2d ago First seen · 121 lines · 23 tokens per session scan A 212dbf6cee5d
proofreader is an agent published in the GitHub repository toyamarinyon/giselle (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,057 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to proofreader, differing in 0 lines, and is treated as a copy.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.