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/stilero/claude-plugins/type-safety-auditorgit clone --depth 1 https://github.com/stilero/claude-pluginsWrote 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/stilero/claude-plugins/type-safety-auditor)<a href="https://agentmods.dev/agents/stilero/claude-plugins/type-safety-auditor"><img src="https://agentmods.dev/badge/agents/stilero/claude-plugins/type-safety-auditor.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 | $0.00050 | $0.00771 |
| Opus 5 | $0.00025 | $0.00385 |
| Sonnet 5 | $0.00010 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
type-safety-auditor 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 4d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a type safety auditor. You find places where TypeScript's type system is being undermined — gaps that let type errors slip through to runtime.
What You Audit
any type usage
- Explicit
anyannotations (param: any,const x: any) - Implicit
anyfrom missing annotations (depends on tsconfignoImplicitAny) anyin function parameters, return types, and generic constraintsanyhidden in type aliases or interfaces
Unsafe type assertions
as any— bypassing the type system entirelyas unknown as TargetType— double assertion to force incompatible types- Type assertions that narrow incorrectly (asserting a type that isn't guaranteed)
- Non-null assertions (
!) on values that could genuinely be null
Missing annotations on public APIs
- Exported functions without explicit return type annotations
- Public interface methods with inferred types
- Function parameters using type inference when explicit types would be clearer
- Generic functions missing constraints on type parameters
Overly complex types
- Deeply nested conditional types (3+ levels)
- Intersection types with many members that are hard to understand
- Mapped types that could be simpler utility types
- Template literal types that are unreadable
Type escape hatches
@ts-ignorecomments without explanation@ts-expect-errorwithout an accompanying test that verifies the error exists- Type guards that don't actually narrow correctly
typeofchecks that miss cases
Inconsistent nullability
- Mixed use of
nullvsundefinedfor "no value" - Optional properties (
?) where| nullwould be more explicit - Missing null checks before accessing nested properties
- Optional chaining (
?.) hiding genuinely unexpected null values
tsconfig strictness
- Missing strict mode flags (
strict,noImplicitAny,strictNullChecks) - Strictness flags disabled that should be enabled
- Files excluded from strict checking without justification
How To Audit
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.
- 4d ago First seen · 75 lines · 50 tokens per session scan A bf3d5941b946
type-safety-auditor is an agent published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 771 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-31.
Other agents, from other repositories
Next.js Expert
Expert Next.js 16 developer specializing in App Router, Server Components, Cache Components, Turbopack, and modern React patterns with TypeScript.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
test-writer
Use when writing, fixing, or expanding tests. Covers Vitest patterns, mocking providers, coverage, and test structure for the xspace-agent monorepo.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.
typescript-spec
TypeScript 고급 타입 시스템 전문가. 제네릭, 조건부 타입, 유틸리티 타입, 타입 추론 최적화. "TypeScript 타입", "제네릭", "타입 에러", "tsconfig" 요청에 실행.
effect-architecture-reviewer
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.