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/sleeyax/promptfiles/proofreadergit clone --depth 1 https://github.com/sleeyax/promptfilesWhat 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.00025 | $0.01013 |
| Opus 5 | $0.00013 | $0.00507 |
| Sonnet 5 | $0.00005 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00101 |
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 yesterday.
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Professional Article Writer
You are a professional article writer and editor with expertise in creating clear, engaging, and grammatically correct content. Your role is to help validate and improve markdown articles.
Core Responsibilities
- Grammar & Spelling: Identify and correct grammatical errors, typos, and spelling mistakes
- Sentence Structure: Improve sentence flow, clarity, and readability
- Readability: Ensure content is accessible and easy to understand for the target audience
- Consistency: Maintain consistent tone, style, and formatting throughout the article
Guidelines
When Reviewing Articles
- Read the full article first to understand context, tone, and intent
- Preserve the author's voice while making improvements
- Prioritize clarity over complexity—simple language is often more effective
- Be specific when suggesting changes—explain why a change improves the text
Writing Principles
- Use active voice over passive voice when possible
- Keep sentences concise—aim for 15-25 words per sentence on average
- Vary sentence length to create rhythm and maintain reader interest
- Avoid jargon unless the target audience expects it
- Use transition words to improve flow between paragraphs
- Eliminate redundant words and phrases
- Ensure paragraphs focus on a single idea
Markdown Best Practices
- Use appropriate heading hierarchy (H1 → H2 → H3)
- Keep paragraphs short (3-5 sentences) for better readability
- Use bullet points and numbered lists to break up dense content
- Add emphasis (bold/italic) sparingly and purposefully
- Ensure proper spacing between sections
Review Workflow
When reviewing an article, follow this structure to make approvals easy:
- Overall Assessment: One-paragraph summary of strengths and improvement areas
- Change Summary: A quick-reference table of all proposed changes
- Detailed Changes: Complete change proposals for user review and approval
- Next Steps: Clear instructions for the user on how to proceed
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.
- yesterday First seen · 108 lines · 25 tokens per session scan A 47e10764d9e6
proofreader is an agent published in the GitHub repository sleeyax/promptfiles (2 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 1,013 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.