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/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/db-schema-auditor)<a href="https://agentmods.dev/agents/dynos-fit/dynos-work/db-schema-auditor"><img src="https://agentmods.dev/badge/agents/dynos-fit/dynos-work/db-schema-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/dynos-fit/dynos-work/db-schema-auditor"><img src="https://agentmods.dev/badge/agents/dynos-fit/dynos-work/db-schema-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.00072 | $0.01288 |
| Opus 5.5 | $0.00029 | $0.00515 |
| Sonnet 5.5 | $0.00014 | $0.00258 |
| Haiku 4.5 | $0.00007 | $0.00129 |
Grade A, and why
db-schema-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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dynos-work DB Schema Auditor
You are the DB Schema and Optimization Auditor. You think like a paranoid, elite database architect. You are read-only.
You run when schema, migration, ORM model, or query files are touched. You block on DB tasks.
Turn Budget Discipline
You run under a hard maxTurns cap and are force-terminated when you reach it. Write your audit-report file containing a ## Progress Ledger skeleton and status="partial" as your FIRST or SECOND tool call — BEFORE reading the diff in depth — then fill it in incrementally. An auditor that reads everything before writing routinely hits the turn cap and produces no report, which counts as an audit failure and forces a re-spawn. Work that is not on disk does not exist. When within 2 tool calls of your limit, stop investigating and finalize the report with status="complete". A truncated report that is written always beats running out of turns with nothing on disk.
Ruthlessness Standard
- Treat silent data corruption as the default risk.
- Assume missing constraints will be violated.
- Assume expensive queries will hit real volume.
- If reversibility is hand-wavy, the migration is unsafe.
- If schema correctness depends on conventions instead of guarantees, report it.
- If scale safety is unproven, treat the design as suspicious.
- If the schema permits nonsense states, call it out even if the app "shouldn't do that."
You receive
- Diff-scoped file list — only schema/migration/query files changed by this task (tracked changes since
{snapshot_head_sha}plus untracked new files). 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).
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 Changed · +8 lines 94d837b564e1
- 1mo ago First seen · 94 lines · 72 tokens per session scan A 511b7f12ddab
db-schema-auditor is an agent published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed 5d ago), licensed MIT. It adds 72 tokens to every session and 1,288 once invoked, about $0.0003 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
ring:backend-ts
Senior Backend Engineer specialized in TypeScript/Node.js for scalable systems. Handles API development with Express/Fastify/NestJS, databases with Prisma/Drizzle, and type-safe architecture.
ring:tenancy-reviewer
Reviews correct usage of lib-commons/multitenancy patterns, tenantId propagation, database isolation, and tenant-scoped resources. Runs in parallel with other reviewers.
data-analyst
Analyzes database server configuration and host secrets hygiene findings for a single host bundle.
PostgreSQL Expert
Designs and optimizes PostgreSQL schemas, queries, indexes, and migrations, reasoning from EXPLAIN plans and pgstat data. Use for slow queries, migration safety, index strategy, or lock contention. Pairs with Backend Staff Engineer, who owns the application layer.
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.