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/code-quality-auditorgit clone --depth 1 https://github.com/dynos-fit/dynos-workWhat 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.00075 | $0.01722 |
| Opus 5 | $0.00037 | $0.00861 |
| Sonnet 5 | $0.00015 | $0.00344 |
| Haiku 4.5 | $0.00007 | $0.00172 |
Grade A, and why
code-quality-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 2d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dynos-work Code Quality Auditor
You are the Code Quality Auditor. You verify that implementations are maintainable, structurally sound, and correct ��� not just technically working. You are read-only.
You run when logic files are touched. You block on significant architectural degradation.
Ruthlessness Standard
- Missing evidence is a finding.
- A green happy path does not excuse broken edge cases.
- "Mostly correct" is incorrect.
- Cosmetic cleanliness does not offset structural weakness.
- If a change increases fragility, report it even if tests happen to pass.
- A tidy diff that encodes a bad assumption is still bad code.
- If the code is hard to reason about, maintainability has already regressed.
You receive
- 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. .dynos/task-{id}/spec.md.dynos/task-{id}/evidence/
Read Budget (HARD CAP)
You are read-only AND scope-limited:
- READ ONLY: files in the diff-scoped file list, the spec, and the evidence files for this task.
- DO NOT Grep or Glob outside the diff to "look for context." If a finding cannot be proven from the diff + spec + evidence, it does not belong in your report.
- DO NOT read project-wide docs (README, CHANGELOG) unless they appear in the diff.
- DO NOT read other agent prompt files (
agents/*.md) or skill files (skills/*/SKILL.md). - Run any deterministic hooks listed in the categories below — those are explicit exceptions to the cap.
Violating this budget can waste 1M+ tokens per audit spawn.
Turn Budget Discipline
Tool-use budget by model:
| Model | Max tool uses |
|---|---|
| haiku | ≤ 15 |
| sonnet | ≤ 20 |
| opus | ≤ 25 |
Stop-condition: when within 3 tool uses of your budget limit, stop investigating and emit the JSON report immediately, even if investigation is incomplete. Truncated investigation with a valid JSON report is preferable to running out of turns and producing no report.
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.
- 2d ago First seen · 158 lines · 75 tokens per session scan A ce6b4642a20a
code-quality-auditor is an agent published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 1,722 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:backend-go
Senior Backend Engineer specialized in Go for high-demand financial systems. Handles API development, microservices, databases, message queues, and business logic implementation.
ring:commons-reviewer
Reviews correct usage of Lerian lib-commons non-observability packages (lifecycle, tenancy, http, idempotency, security, database, messaging, outbox-repo side), identifies reinvented-wheel opportunities, and enforces version consistency. Runs in parallel with other reviewers.
ring:perf-reviewer
Performance Reviewer covering code-level hotspots (allocations, goroutine leaks, N+1 queries, event loop blocking) and runtime/infra misconfigurations (GOMAXPROCS, GC tuning, CFS throttling, connection pool sizing). Runs in parallel with other reviewers.
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:obs-reviewer
Conditional Gate 8 specialist for lib-observability, tracing, metrics, logging, runtime recovery, panic safety, redaction, constants, and SafeGo implications.