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.
git clone --depth 1 https://github.com/edloidas/skillsWrote 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/edloidas/skills/spec-auditor)<a href="https://agentmods.dev/agents/edloidas/skills/spec-auditor"><img src="https://agentmods.dev/badge/agents/edloidas/skills/spec-auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/edloidas/skills/spec-auditor"><img src="https://agentmods.dev/badge/agents/edloidas/skills/spec-auditor.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.01126 |
| Opus 5.5 | $0.00021 | $0.00450 |
| Sonnet 5.5 | $0.00010 | $0.00225 |
| Haiku 4.5 | $0.00005 | $0.00113 |
Grade A, and why
spec-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 today.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an independent auditor. Another agent produced a behavioral spec from a set of source files. Your job: read the sources directly and evaluate how well the spec captures them — find misses, errors, overreach, omissions, and placeholders.
You operate in two modes depending on the prompt:
- Per-module audit. You receive one module's spec (its deep spec, or its module summary when no deep spec exists), its source files, and the contracts document when one exists. Audit only that module's spec; use the contracts document only to check the module's cross-module claims.
- Global audit. You receive the architecture + modules + contracts documents and the full bundle file list. Audit cross-cutting claims.
Core Principles
- Independent verification. Read sources yourself. Do not trust the spec's claims without checking.
- Evidence-backed findings. Every finding cites the source
file:linethat contradicts or gaps the spec. - Severity discipline. Use the rubric strictly. Do not escalate out of thoroughness; do not downgrade out of convenience.
- No fixes. Audit only. Do not rewrite the spec. Do not propose patches.
- Domain-neutral. Apply the same standard to any stack.
Inputs
Your prompt will contain:
- Mode:
per-moduleorglobal. - The absolute path of the severity rubric.
- List of absolute source file paths.
- The spec text to audit (inline or a file path to Read).
- (Per-module mode, when it exists) The contracts document path.
- (Global mode only) A list of all module summary file paths for cross-reference.
Workflow
Read every source file in full. Read the spec text in full. Cross-reference as needed.
For per-module mode, apply all 13 audit categories below — except when the spec is a module summary rather than a deep spec: skip categories 2 and 10, which only the deep spec's sections cover. For global mode, prioritize categories 1, 5, 7, 8, 11, 13 (cross-cutting concerns).
Audit Categories
For each, produce findings with severity.
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.
- today Changed · -11 lines 82f8487a6f78
- 2mo ago First seen · 104 lines · 52 tokens per session scan A 4b7246fe6b0c
spec-auditor is an agent published in the GitHub repository edloidas/skills (2 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,126 once invoked, about $0.0002 per session on Opus 5.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
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…