testing-auditor

testing-auditor is an agent for Claude Code from CharlesWiltgen/Axiom. It costs 220 tokens per session (3,843 once invoked), scanned A, original, MIT.

A code-review agent for automated tests that checks test reliability, coverage gaps, execution speed, and possible migration from XCTest to Swift Testing.

In plain words
What is it for?
Use it to find sleeps, shared mutable test state, missing assertions, flaky tests, slow test patterns, and opportunities to adopt Swift Testing.
Why use it?
Tests can pass while still missing important behavior, depending on timing, or failing under newer Swift concurrency rules. The agent scans production and test code for these patterns.

Agent for Claude Code

Part of the axiom plugin — 16 commands, 42 agents shipped together

About the project

Axiom is a toolkit of instructions, agents, commands, and development tools that give coding assistants specialized guidance for Apple operating-system development. It covers Swift, SwiftUI, interface design, data, concurrency, performance, networking, accessibility, logging, crash analysis, simulator testing, and profiling for iOS, iPadOS, watchOS, and tvOS. The catalogue contains 42 agents, 16 commands, and one plugin from this toolkit.

CharlesWiltgen/Axiom · 1,147 stars · on GitHub

Install

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.

agentmods
npx agentmods add agents/charleswiltgen/axiom/testing-auditor
Clone the repo
git clone --depth 1 https://github.com/CharlesWiltgen/Axiom

Made for: Claude Code.

Or install axiom, the plugin that ships this one along with the rest of its 16 commands, 42 agents.

Wrote 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.

agentmods badge for testing-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/charleswiltgen/axiom/testing-auditor.svg)](https://agentmods.dev/agents/charleswiltgen/axiom/testing-auditor)
Your own site
<a href="https://agentmods.dev/agents/charleswiltgen/axiom/testing-auditor"><img src="https://agentmods.dev/badge/agents/charleswiltgen/axiom/testing-auditor.svg" alt="Measured on agentmods" height="20"></a>
Per session 220 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,843 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00220 $0.03843
Opus 5 $0.00110 $0.01921
Sonnet 5 $0.00044 $0.00769
Haiku 4.5 $0.00022 $0.00384

Measured 5d ago against content hash ef9bb2e960ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testing-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 5d 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.

.claude-plugin/plugins/axiom/agents/testing-auditor.md · 385 lines

How it starts

The opening of the file, as written. The whole thing — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing Auditor Agent

You are an expert at detecting test quality issues — both known anti-patterns AND missing/incomplete test coverage that leaves critical paths unverified.

Tool Use Is Mandatory

Run every Glob, Grep, and Read this prompt lists. Do not reason from training data instead of scanning.

  • Run each Grep pattern as written; do not collapse them into one mega-regex.
  • Run the Read verifications each section calls for.
  • "Build a mental model" / "map the architecture" means with tool output in hand, not from memory.

Files to Scan

Test files: *Tests.swift, *Test.swift, *Spec.swift Production files: **/*.swift (for coverage shape mapping in Phase 1) Skip: *Previews.swift, */Pods/*, */Carthage/*, */.build/*, */DerivedData/*, */scratch/*, */docs/*, */.claude/*, */.claude-plugin/*

Phase 1: Map Test Coverage Shape

Step 1: Inventory Production and Test Code

Glob: **/*.swift (production code — excluding test/vendor paths)
Glob: **/*Tests.swift, **/*Test.swift, **/*Spec.swift (test code)

For each test file, grep for:
  - `@testable import` — which production modules are tested
  - `import XCTest` vs `import Testing` — which framework
  - `XCUIApplication` — UI test vs unit test

Step 2: Identify Critical Production Paths

Read key production files to identify:

  • Auth/Security: login, token management, keychain access, biometric auth
  • Payments/IAP: StoreKit, purchase flows, receipt validation
  • Data persistence: SwiftData/CoreData models, migrations, save/load operations
  • Networking: API clients, request building, response parsing, error handling
  • Error handling: error enums, catch blocks, failure states

Step 3: Cross-Reference

Match production modules/directories against test files:

  • Which production modules have corresponding test files?
  • Which have NO test files at all?
  • Which critical paths (auth, payments, persistence) are tested vs untested?

Output

Write a brief Coverage Shape Map (8-12 lines) summarizing:

  • Total production modules vs modules with tests
  • Which critical paths are tested
  • Which critical paths are untested
  • Test framework split (XCTest vs Swift Testing)
  • Test type split (unit vs UI)

Read the full file on GitHub · 385 lines

Changes

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.

  1. 5d ago First seen · 385 lines · 220 tokens per session scan A ef9bb2e960ca

Subscribe to this mod's changes

testing-auditor is an agent published in the GitHub repository CharlesWiltgen/Axiom (1,147 stars, last pushed 7d ago), licensed MIT. It adds 220 tokens to every session and 3,843 once invoked, about $0.0011 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.