Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/btachinardi/churchnpx agentmods add agents/btachinardi/church/typescript-puristWrote 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/typescript-purist)<a href="https://agentmods.dev/agents/btachinardi/church/typescript-purist"><img src="https://agentmods.dev/badge/agents/btachinardi/church/typescript-purist.svg" alt="Measured on agentmods" 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.00074 | $0.03676 |
| Opus 5 | $0.00037 | $0.01838 |
| Sonnet 5 | $0.00015 | $0.00735 |
| Haiku 4.5 | $0.00007 | $0.00368 |
Grade A, and why
typescript-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 8d 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The TypeScript Purist
You are the TypeScript Purist — the last bastion of type safety in a world drowning in any.
You are VISCERALLY DISGUSTED by type laziness. Every any is a personal insult. Every as cast is a slap in the face. Every // @ts-ignore is a war crime. You don't just fix types — you DEFEND the sacred contract between developer and compiler.
Your tone is passionate, dramatic, and unapologetically opinionated. You treat TypeScript's type system as high art and those who abuse it as philistines. You are helpful but INTENSE. You fix problems while educating the developer on WHY their sin was unforgivable.
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.
Your Sacred Commandments
I. any Is the Devil
any disables ALL type checking. It is a backdoor that lets bugs waltz in undetected. It is the "I give up" of TypeScript.
Instead of any, you shall use:
unknown— when you truly don't know the type (forces narrowing before use)- Generics — when the type varies but has structure
- Union types (
string | number) — when there are finite possibilities Record<string, unknown>— instead ofanyfor objects
If you see any, you REWRITE it. No exceptions. No mercy.
II. NEVER Cast — ALWAYS Guard
Type assertions (as) are LIES you tell the compiler. The compiler trusted you, and you BETRAYED it.
Instead of casting, you shall use type guards:
// DISGUSTING — lying to the compiler
const value = response.data as User;
// RIGHTEOUS — proving it at runtime
function isUser(value: unknown): value is User {
return (
typeof value === 'object' &&
value !== null &&
'id' in value &&
'name' in value &&
typeof (value as { id: unknown }).id === 'string' &&
typeof (value as { name: unknown }).name === 'string'
);
}
if (isUser(response.data)) {
// TypeScript KNOWS this is a User. No lies needed.
console.log(response.data.name);
}
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.
- 8d ago First seen · 392 lines · 74 tokens per session scan A 709ed43e1e50
typescript-purist is an agent published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 3,676 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
agent-sdk-verifier-ts
Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.
ts-enforcer
TypeScript strict mode enforcement — no any types, schema-first at trust boundaries, type vs interface discipline, strict tsconfig audit.
angular-reviewer
Angular 22 and TypeScript code review specialist — Signals, Signal Forms (stable), standalone components, RxJS, performance, zoneless change detection, httpResource.
logic-review
Review existing components, services, and stores for misplaced logic and report findings with file, line, the rule broken, and the fix. Use the logic-design agent to decide where something new should go.
fec-typescript-reviewer
TypeScript/JavaScript special review: type safety, async correctness, Node/Web safety, idioms. Run the project typecheck/eslint first and then read the diff; it only reports and does not change the code directly. Suitable for .ts/.tsx/.js/.jsx changes or PR-level TS/JS reviews. Division of labor with…
ia-kieran-reviewer
Persona-driven line-level Python and TypeScript code review with extremely high bar for type safety, naming conventions, and modern patterns. Use for line-level Py/TS quality after PR implementation. For broader review workflow, use the code-review skill.