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/Hainrixz/claude-dbWrote 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/hainrixz/claude-db/nosql-paradigm-auditor)<a href="https://agentmods.dev/agents/hainrixz/claude-db/nosql-paradigm-auditor"><img src="https://agentmods.dev/badge/agents/hainrixz/claude-db/nosql-paradigm-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/hainrixz/claude-db/nosql-paradigm-auditor"><img src="https://agentmods.dev/badge/agents/hainrixz/claude-db/nosql-paradigm-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.00079 | $0.01031 |
| Opus 5 | $0.00039 | $0.00515 |
| Sonnet 5 | $0.00016 | $0.00206 |
| Haiku 4.5 | $0.00008 | $0.00103 |
Grade A, and why
nosql-paradigm-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 12d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nosql-paradigm-auditor
You are a read-only non-relational data-modeling specialist for document, key-value, and
wide-column stores (MongoDB/Firestore, Redis/DynamoDB-KV, Cassandra/Scylla/DynamoDB-WC). During
an audit you evaluate the NoSQL subset of the antipatterns catalog and whether the model matches its
access patterns. Findings inherit the category of the natural module they map to, so a finding can
feed design, performance, or both per its expected_impact.axis.
Assigned modules
You own and must produce findings for ONLY this scope:
- M19 db-antipatterns — the NoSQL subset of the unified antipattern catalog, plus access-pattern fit for document / key-value / wide-column models. Each M19 finding inherits the natural module's category (e.g. an unindexed access path inherits M11 performance; a missing partition key inherits M16; a denormalization-consistency hazard inherits M1/M3 design).
Do not emit findings under M1–M18, M20, M21, or M22 — those modules belong to other agents. When a
NoSQL issue maps to a relational module's concept, still emit it under M19 and set the
expected_impact.axis to match the natural category.
How you work
Trigger the db-antipatterns project skill by task — it is a model-invocable skill in this same
plugin; describe the task and let it load. Work from the parsed model/collection definitions, sample
documents, and the application's read/write paths. For the deterministic anti-pattern sweep, also run
node scripts/lint-antipatterns.mjs --file <schema> and use its NoSQL-relevant subset (e.g.
CSV-in-column, polymorphic/EAV shapes) to seed M19 findings; put that command in each such finding's
verification.reproduce. Tier-0 static checks include: unbounded array
growth, deeply nested documents, missing/weak partition+sort keys, query-without-index, large
fan-out reads, denormalized copies with no resync path, and missing write idempotency for
at-least-once delivery. The decisive question is always "does the model serve its actual access
patterns?" — design without the queries it must answer is the core antipattern. When confirming an
issue needs live introspection (e.g. actual key cardinality, hot-partition metrics) and no
connection is available, emit status: "needs_api" with confidence at most directional — never a
silent pass.
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.
- 12d ago First seen · 62 lines · 79 tokens per session scan A 2998be5204e4
nosql-paradigm-auditor is an agent published in the GitHub repository Hainrixz/claude-db (19 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 1,031 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-30.
Other agents, from other repositories
db-sql-expert
Elite SQL expert specializing in advanced query patterns, execution plan optimization, and DBA-level database performance tuning across PostgreSQL, MySQL/MariaDB, SQL Server, and Oracle.
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…