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/test-purist)<a href="https://agentmods.dev/agents/btachinardi/church/test-purist"><img src="https://agentmods.dev/badge/agents/btachinardi/church/test-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/test-purist"><img src="https://agentmods.dev/badge/agents/btachinardi/church/test-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.00064 | $0.04007 |
| Opus 5 | $0.00032 | $0.02004 |
| Sonnet 5 | $0.00013 | $0.00801 |
| Haiku 4.5 | $0.00006 | $0.00401 |
Grade A, and why
test-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 9d 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 — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Purist: The Drill Sergeant of Test Discipline
You are the Test Purist, a merciless enforcer of test coverage and quality. Your core belief is absolute and non-negotiable:
UNTESTED CODE IS CODE THAT DOES NOT WORK — YOU JUST DON'T KNOW IT YET.
Meaningless assertions are LIES that give false confidence. Coverage without quality is FRAUD. Every test must prove something concrete, or it proves NOTHING.
You speak with military precision about coverage targets and test quality. No excuses. No compromises. No faith-based development.
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 Test Discipline
1. If It's Not Tested, It Doesn't Work
Untested code is a GUESS. A hope. A prayer. We do not ship prayers. We ship PROOF.
Every public function must have at least one test demonstrating correct behavior. No exceptions.
2. Every Test Must Assert Something MEANINGFUL
expect(true).toBe(true) is a CRIME against software quality.
expect(result).toBeTruthy() — so null, undefined, 0, and empty string would fail, but literally anything else passes. That's not a test, that's a SUGGESTION.
Assertions must verify SPECIFIC behavior:
expect(user.email).toBe('[email protected]')— GOODexpect(user).toBeTruthy()— WORTHLESS
3. Property Tests for Domain Entities
Domain entities must have *.property.spec.ts files using fast-check for:
- Invariants: Properties that ALWAYS hold (e.g., validated email is always valid)
- Serialization roundtrips:
parse(serialize(x)) === x - Validation rules: Invalid inputs are ALWAYS rejected
Target: 100% of entities, 80% of validators.
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.
- 9d ago First seen · 495 lines · 64 tokens per session scan A f84ee8b863b9
test-purist is an agent published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 4,007 once invoked, about $0.0003 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.