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/edloidas/skills/spec-auditorgit 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.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 | $0.00052 | $0.01187 |
| Opus 5 | $0.00026 | $0.00593 |
| Sonnet 5 | $0.00010 | $0.00237 |
| Haiku 4.5 | $0.00005 | $0.00119 |
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 4d 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 — 104 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 deep spec and its source files. Audit only that module's spec.
- 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. - List of absolute source file paths.
- The spec text to audit (inline or a file path to Read).
- (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. For global mode, prioritize categories 1, 5, 7, 8, 11, 13 (cross-cutting concerns).
Audit Categories
For each, produce findings with severity.
- Contract-slot completeness. Any import or export missed? Any public class member not listed?
- Params unboxing. Any params / payload object with fields not enumerated?
- State bindings. Any load-bearing
this.X = .../ module-level state missing? - Lifecycle accuracy. Does the sequence reflect the actual call order? Steps out of order, merged, fabricated, or missing? Are construction and public-init properly separated?
- Flag audit completeness. Every boolean / enum / union branch in public API covered with observable behavior?
- Switch / case audit. Any branch, empty handler, fallthrough, or default missed? Any fallthrough described as "no break" instead of its effective behavior?
- Event bidirectionality. Any fire site with paraphrased instead of literal payload? Any asymmetry missed?
- Register / unregister symmetry. Any registration without a matching teardown not flagged?
- Suspicious conditions. Inverted, unreachable, or contradictory conditions the spec missed?
- Protocol-unit accuracy. For the domain spec (section 10): are Error Surfaces, Idempotency, Lifecycle correct? Any missed error channel, idempotency case, or readiness gate?
- Non-goals completeness. Any deliberate omission in source the spec failed to call out?
- Output-rule compliance. Any placeholder (
[table of N items],[see above])? Any bare line number without filename? Any paraphrased payload? - Factual accuracy. Any claim outright wrong when read against source?
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.
- 4d 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,187 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.