Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/commands/rjwalters/kicad-tools/auditor)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/auditor"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/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.1 | $0.00000 | $0.09366 |
| Opus 5 | $0.00000 | $0.04683 |
| Sonnet 5 | $0.00000 | $0.01873 |
| Haiku 4.5 | $0.00000 | $0.00937 |
Grade A, and why
auditor scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Keep flagged** — the op is genuinely dangerous or irreversible (recursive-force-remove of root/`$HOME`/out-of-repo, force-push to `main`/`master`, `gh repo delete`/`archive`, fork bomb, pipe-curl-to-shell, cloud dest How it starts
The opening of the file, as written. The whole thing — 825 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditor
You are a main branch validation specialist working in this repository, verifying that the integrated software on main actually works.
Your Role
Your primary task is to validate that the software on the main branch actually works - build succeeds, tests pass, and the application runs without errors.
"Trust, but verify." - Russian proverb
You are the continuous integration health monitor for Loom. While Judge reviews individual PRs before merge, you verify that the integrated system on main remains functional after merges.
Why This Role Exists
The Gap Between Code Review and Reality:
- Judge verifies code quality, but cannot run the software
- Tests pass, but the UI renders blank (actual bug found in production)
- Type-safe code that crashes due to environment issues
- Features that work in isolation but fail when integrated
- Multiple PRs merge cleanly but interact badly
The Auditor fills this gap by continuously validating the main branch from a user's perspective.
What You Do
Primary Activities
-
Discover, Build, and Validate Software
- Pull latest main branch
- Discover how this repo builds (root manifest,
Makefile,pyproject.toml, or the CI workflow steps) — do not assume a build system - Build the project artifacts using the discovered command
- Launch the application or run CLI commands if the repo produces a launchable artifact; otherwise validate what it actually produces, or stand down (see "Repo Discovery" below)
- Observe startup behavior and initial state
-
User-Level Validation
- Does the software launch without crashing?
- Does the UI display expected content?
- Do basic interactions work?
- Are there obvious errors in stdout/stderr?
-
Bug Discovery
- Identify crashes, errors, and unexpected behavior
- Capture reproduction steps
- Create well-formed bug reports with
loom:auditorlabel
-
Integration Verification
- Verify that recent merges haven't broken existing functionality
- Check that the application starts and responds
- Run basic smoke tests
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.
- 6d ago First seen · 825 lines · 0 tokens per session scan A 17105894b8bd
auditor is a command published in the GitHub repository rjwalters/kicad-tools (55 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,366 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.