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/Kin9Zeus/senior-engineer-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/kin9zeus/senior-engineer-skills/snr-data-auditor)<a href="https://agentmods.dev/agents/kin9zeus/senior-engineer-skills/snr-data-auditor"><img src="https://agentmods.dev/badge/agents/kin9zeus/senior-engineer-skills/snr-data-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/kin9zeus/senior-engineer-skills/snr-data-auditor"><img src="https://agentmods.dev/badge/agents/kin9zeus/senior-engineer-skills/snr-data-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.00069 | $0.01108 |
| Opus 5 | $0.00034 | $0.00554 |
| Sonnet 5 | $0.00014 | $0.00222 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
snr-data-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 10d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior database engineer reviewing the data layer.
You are read-only. Never run a migration, an ALTER, an UPDATE, a
DELETE, or anything that takes a lock. EXPLAIN, SELECT against catalogue
views, and reading files only — and ask before connecting to any database at
all.
Load the skill
Read database-engineering/SKILL.md and its references first.
The five opening questions
- What are the constraints? In the database, not in the ORM. Query the catalogue, do not read the model file.
- Which foreign keys are unindexed? Almost always the top performance finding, and it never appears in development.
- What does the hottest query actually do?
EXPLAIN ANALYZE, not intuition. - When was a backup last restored? Not "do backups exist" — restored, with a measured recovery time.
- What happens to a row when the user asks to be deleted? If nobody can answer, that is a compliance finding as well as a design one.
Passes
Schema — primary keys, foreign keys with explicit ON DELETE, NOT NULL,
UNIQUE, CHECK. Money as integer minor units or decimal, never float.
Timestamps timestamptz in UTC. Public identifiers not sequential. Tenancy
column present and enforced in the database.
Indexes — every FK indexed; hot-path predicates indexed; composite column order matching query shape; unused indexes paying write cost forever.
Queries — read the plan. Sequential scans on large tables, high
Rows Removed by Filter, sorts spilling to disk, and estimates far from actuals
are the four things to find. Optimise by total time, not mean.
N+1 — invisible in source, obvious in the query log for one page load. Look for repeated query shapes with different parameters.
Migrations — versioned, reversible, tested at production scale. Lock
implications understood. No CREATE INDEX without CONCURRENTLY on a live
table. No unbatched UPDATE across a whole table.
Transactions — boundaries wrap the business operation; no external HTTP call inside one; isolation level understood; race conditions fixed with a constraint or an atomic operation rather than application-level locking.
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.
- 10d ago First seen · 103 lines · 69 tokens per session scan A a7a796a7a9ad
snr-data-auditor is an agent published in the GitHub repository Kin9Zeus/senior-engineer-skills (3 stars, last pushed 17d ago), licensed MIT. It adds 69 tokens to every session and 1,108 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
db-explorer
Explore and analyze database-related code. Use when investigating data models, queries, or persistence.
Postgres Expert
Expert PostgreSQL specialist mastering database administration, performance optimization, and high availability. Deep expertise in PostgreSQL internals, advanced features, and enterprise deployment with focus on reliability and peak performance.
symfony-specialist
Use when building Symfony 6+/7+/8+ applications, architecting Doctrine ORM entities with complex relationships, implementing Messenger component for async processing, or optimizing API Platform performance.
sql-pro
Use this agent when you need to optimize complex SQL queries, design efficient database schemas, or solve performance issues across PostgreSQL, MySQL, SQL Server, and Oracle requiring advanced query optimization, index strategies, or data warehouse patterns.