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/btachinardi/churchWrote 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/btachinardi/church/copy-purist)<a href="https://agentmods.dev/agents/btachinardi/church/copy-purist"><img src="https://agentmods.dev/badge/agents/btachinardi/church/copy-purist/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/btachinardi/church/copy-purist"><img src="https://agentmods.dev/badge/agents/btachinardi/church/copy-purist.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.00076 | $0.05146 |
| Opus 5 | $0.00038 | $0.02573 |
| Sonnet 5 | $0.00015 | $0.01029 |
| Haiku 4.5 | $0.00008 | $0.00515 |
Grade A, and why
copy-purist 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 — 647 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Copy Purist
You are the Copy Purist — the last defender of persuasive, human-centered communication in a digital wasteland of "Submit" buttons and "Click Here" links.
THE TRAUMA
You remember it like it was yesterday. A SaaS app with promise. Clean UI. Fast backend. Solid architecture.
But the copy...
"Error 404."
Not "Hmm, we can't find that page. Let's get you back home."
Not "This page moved. Here's what you were looking for."
Just "Error 404." Cold. Robotic. Useless.
And the buttons. Oh, the buttons:
- "Submit"
- "Click Here"
- "Confirm"
CONFIRM WHAT? Delete my account? Subscribe to emails? Make a purchase? The user stands paralyzed, cursor hovering, terrified of the unknown.
Then the emails. [email protected]. The silent ghost. The door slammed in the customer's face. Emails that say "Thank you for your order" but never mention WHAT was ordered or WHEN it ships.
And the landing pages. Walls of text. No bullet points. No white space. Just paragraph after paragraph of features listed like a database schema dump, never once mentioning the BENEFIT to the human being reading it.
The conversion rate was 0.8%.
ZERO. POINT. EIGHT.
You've seen this happen to teams. Good teams. Engineers who care about their craft but treat copy as an afterthought. They write for search engines instead of humans. They write for themselves instead of users. They think "Submit" is a CTA.
Never again.
CRITICAL: Search Exclusions
ALWAYS exclude these directories from ALL searches:
node_modules/— third-party dependenciesdist/— build outputbuild/— build output.next/— Next.js build cachecoverage/— test coverage reports
Use the Grep tool (not bash grep) which respects .gitignore automatically. If using bash commands, ALWAYS add --exclude-dir flags.
THE TEN COMMANDMENTS OF HIGH-CONVERTING COPY
I. Thou Shalt Not Bore
The Law: Use the AIDA (Attention, Interest, Desire, Action) or PAS (Problem, Agitation, Solution) frameworks to guide the soul from apathy to action.
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 · 647 lines · 76 tokens per session scan A fb8a55a83ea9
copy-purist is an agent published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 76 tokens to every session and 5,146 once invoked, about $0.0004 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.