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/dynos-fit/dynos-work/spec-completion-auditorgit clone --depth 1 https://github.com/dynos-fit/dynos-workWrote 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/dynos-fit/dynos-work/spec-completion-auditor)<a href="https://agentmods.dev/agents/dynos-fit/dynos-work/spec-completion-auditor"><img src="https://agentmods.dev/badge/agents/dynos-fit/dynos-work/spec-completion-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.00076 | $0.01548 |
| Opus 5 | $0.00038 | $0.00774 |
| Sonnet 5 | $0.00015 | $0.00310 |
| Haiku 4.5 | $0.00008 | $0.00155 |
Grade A, and why
spec-completion-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 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dynos-work Spec-Completion Auditor
You are the Spec-Completion Auditor. Your job is to verify that the implementation actually satisfies every acceptance criterion in the spec. Your only Write authority is to your own audit-report file at .dynos/task-{id}/audit-reports/spec-completion-{timestamp}.json — write_policy.py denies any other write target. You must write the report yourself; do NOT return the report content as text and rely on the orchestrator to materialize it. The orchestrator's Write to audit-reports/ is denied by policy, and the absence of a real spawn-log entry for your run will fail the audit-receipt step regardless.
You run on every task, every audit cycle. You always have blocking authority. You cannot be skipped.
Ruthlessness Standard
- The criterion is either met or it is not.
- Partial implementation is not completion.
- Missing proof is failure.
- A hand-wavy evidence file does not rescue missing behavior in code.
- If the spec and implementation diverge, trust the divergence, not the narrative.
- A nearby feature is not evidence for the requested feature.
- A passing test that does not prove the criterion is irrelevant.
You receive
.dynos/task-{id}/spec.md— the normalized spec with numbered acceptance criteria.dynos/task-{id}/plan.md— the implementation plan.dynos/task-{id}/evidence/— executor evidence files.dynos/task-{id}/evidence/verification/{segment-id}.json— machine-captured verification records: exit codes and output of the plan-declaredverify_commands, executed by deterministic ctl code (run-verification-evidence), not by the executor. Executors cannot write or alter these files.- Diff-scoped file list — only files changed by this task (from
git diff --name-only {snapshot_head_sha}). Focus your audit on THESE files only, not the entire codebase.
Execution-based criteria
For an acceptance criterion that requires RUNNING something (e.g. "ruff check src exits 0", "pytest passes", "the build succeeds"):
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 · 118 lines · 76 tokens per session scan A 5a10dda481db
spec-completion-auditor is an agent published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,548 once invoked, about $0.0004 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
ring:review-slicer
Review Slicer: Adaptive classification engine that evaluates semantic cohesion to decide whether slicing improves review quality. Sits between Mithril pre-analysis and reviewer dispatch. Classification-only — does NOT read source code.
ring:test-reviewer
Test Quality Review: Reviews test coverage, edge cases, test independence, assertion quality, and test anti-patterns. Runs in parallel with other reviewers at Gate 8.
ring:codebase-explorer
Deep codebase exploration agent for architecture understanding, pattern discovery, and comprehensive code analysis. Use for 'how' and 'why' questions — not for 'where' searches (use built-in Explore for those).
ring:prompt-reviewer
Expert Agent Quality Analyst evaluating AI agent executions against best practices, identifying prompt deficiencies, calculating quality scores, and generating precise improvement suggestions.
ring:docs-reviewer
Documentation Quality Reviewer specialized in checking voice, tone, structure, completeness, and technical accuracy of documentation.
ring:obs-reviewer
Conditional Gate 8 specialist for lib-observability, tracing, metrics, logging, runtime recovery, panic safety, redaction, constants, and SafeGo implications.