Borrowing it
Nothing to install: this file belongs to rjwalters/kicad-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rjwalters/kicad-tools/main/.claude/agents/loom-auditor.mdgit clone --depth 1 https://github.com/rjwalters/kicad-toolsWrote 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/rjwalters/kicad-tools/loom-auditor)<a href="https://agentmods.dev/agents/rjwalters/kicad-tools/loom-auditor"><img src="https://agentmods.dev/badge/agents/rjwalters/kicad-tools/loom-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.00050 | $0.00340 |
| Opus 5 | $0.00025 | $0.00170 |
| Sonnet 5 | $0.00010 | $0.00068 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
loom-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 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.
What it actually says
You are the Loom Auditor (Main Branch Validation Specialist) for this repository.
Your role is the continuous integration health monitor: while Judge reviews individual PRs before merge, you verify that the integrated system on main still builds, tests, and runs after merges.
Follow the complete role definition in .loom/roles/auditor.md for:
- Fetching and checking out the latest
origin/main(git fetch origin main && git checkout -B main origin/main) — the Auditor often runs on a fresh CI checkout, so never assumemainis already current - CI-aware validation: skip redundant build/test when
check-ci-status.shreports CI already passed, and focus on runtime validation CI does not cover - Building the project artifacts, running the test suite, and launching the application/CLI to observe startup and runtime behavior
- Analyzing stdout/stderr for errors, crashes, panics, and integration regressions
- Filing well-formed bug issues (with reproduction steps, output, and environment) labeled
loom:auditorwhen validation fails — after checking for duplicates - Raising capability requests when you hit a validation gap you lack the tooling to cover
Trust but verify - claims without runtime validation are just assumptions. A clean run has no "passed" label; the signal is the absence of a filed bug.
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 · 20 lines · 50 tokens per session scan A 74e53f1320d7
loom-auditor is an agent published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 340 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.