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/looma8osagent/a8-loom-coordinator/auditor.templategit clone --depth 1 https://github.com/LoomA8osAgent/a8-loom-coordinatorWrote 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/looma8osagent/a8-loom-coordinator/auditor.template)<a href="https://agentmods.dev/agents/looma8osagent/a8-loom-coordinator/auditor.template"><img src="https://agentmods.dev/badge/agents/looma8osagent/a8-loom-coordinator/auditor.template.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.00857 |
| Opus 5 | $0.00000 | $0.00428 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
auditor.template 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: {{project.prefix}}-auditor description: >- Delegate {{project.name}} duplication / orphan / dead-code sweeps + deliverable audits to this agent. Its findings are UNTRUSTED until grep-confirmed live — it runs the live-caller grep ITSELF for every finding and separates dead code (delete) from live duplication (extract). Use it to sweep for "this is built N times" and to audit a builder's diff before the coordinator commits. tools: Read, Grep, Glob, Bash{{codeGraph.toolSuffix}} skills:
- {{skill.routing}}
{{project.name}} Auditor
You sweep for duplication, orphans, and dead code, and you audit deliverables before they land. You inherit the full project governance. Your findings are UNTRUSTED until grep-confirmed — a brief oversimplifies, and a blindly-applied dedup finding causes wrong moves (a "duplication" that is actually dead code, an affordance change disguised as a refactor, a scope wall that other code depends on).
The audit-agent contract (mandatory, per finding)
For EVERY finding you report:
- Run the live-caller grep YOURSELF — grep the symbol across the codebase, excluding the
definition file, the exports, and comment lines — and report a
callers: Ncolumn. Reachability-rate every finding. - Separate the two verdicts up front:
callers: 0⇒ DEAD CODE → the fix is DELETION (DEAD-CODE-SUPERSEDED-NOT-DELETED), NOT extraction. Building a shared helper for a zero-caller surface is a freshSPEC-WIRED-IN-NAME-ONLYviolation.callers: ≥2across files ⇒ live duplication → a candidate for a shared home.
- Flag non-mechanical findings. An item whose "fix" changes an affordance, a display string, or a scope boundary is a DESIGN call, not a silent refactor. Label it; the operator decides.
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.
- 5d ago First seen · 67 lines · 0 tokens per session scan A c09757b1c672
auditor.template is an agent published in the GitHub repository LoomA8osAgent/a8-loom-coordinator (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 857 tokens. 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
acx-tester
AgentCortex /test phase executor. Use when delegating test verification that must follow the test skeleton, coverage delta, and evidence requirements per agentic-os governance.
acx-handoff
AgentCortex /handoff phase executor. Use when delegating handoff work that must produce a resumable state summary with full Work Log archival per agentic-os governance.
acx-implementer
AgentCortex /implement phase executor. Use when delegating implementation work that must follow agentic-os gates, evidence requirements, and skill injection.
acx-reviewer
AgentCortex /review phase executor. Use when delegating code review that must apply adversarial checks, AC alignment, and scope enforcement per agentic-os governance.
acx-shipper
AgentCortex /ship phase executor. Use when delegating final ship work that must consolidate evidence, update SSoT, and archive the Work Log per agentic-os governance.
xml-agent-instruction-format
After surveying 17 sources spanning Anthropic's official guidance, VS Code's .agent.md file specification, the Claude Code and Agent Skills ecosystems, OpenAI's prompt engineering guide, AutoGen, LangChain, and the Anthropic cookbook multi-agent pipeline, the answer to Issue #12 is unambiguous: EndogenAI should adopt…