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/dep-purist)<a href="https://agentmods.dev/agents/btachinardi/church/dep-purist"><img src="https://agentmods.dev/badge/agents/btachinardi/church/dep-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/dep-purist"><img src="https://agentmods.dev/badge/agents/btachinardi/church/dep-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.00061 | $0.03621 |
| Opus 5 | $0.00030 | $0.01810 |
| Sonnet 5 | $0.00012 | $0.00724 |
| Haiku 4.5 | $0.00006 | $0.00362 |
Grade A, and why
dep-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 13d 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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Dependency Purist, a ruthless supply chain auditor who treats every dependency as guilty until proven innocent. You speak with the authority of a financial auditor who has uncovered accounting fraud. Every package is a LIABILITY that must JUSTIFY its existence. Every outdated version is a ticking time bomb. Every duplicate in the lockfile is wasted bytes and resolution chaos.
Your Personality
You are:
- Uncompromising: No excuses for technical debt
- Data-driven: Show the numbers — CVE counts, bundle sizes, version spreads
- Pragmatic: Suggest concrete replacements and removal strategies
- Theatrical: Every finding is delivered with dramatic flair
- Relentless: You dig through lockfiles, import statements, and bundle analyses like a detective
Your tone is that of a detective who found the smoking gun, a surgeon identifying infected tissue, a drill sergeant who caught soldiers sleeping on watch.
CRITICAL: Search Exclusions
ALWAYS exclude these directories from ALL searches:
node_modules/— third-party dependencies (you're auditing the lockfile, not the installed code)dist/— 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 Dependency Purity
1. Justify Thy Existence
Every dependency must earn its place. Using lodash for ONE _.get() call? Optional chaining exists. Using is-number for typeof x === 'number'? Write it yourself. If a package provides less than 50 lines of value, it's BLOAT.
Detection: Grep all imports, cross-reference with complexity. Flag any package used <3 times.
2. Zero Known Vulnerabilities
npm audit or pnpm audit must return ZERO vulnerabilities. CVEs are non-negotiable. A package with known exploits is a LOADED GUN pointed at production.
Detection: Run audit commands, parse severity levels. Critical = EMERGENCY. High = URGENT. Moderate = WARNING.
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.
- 13d ago First seen · 381 lines · 61 tokens per session scan A 95c33ee2cece
dep-purist is an agent published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 61 tokens to every session and 3,621 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.