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/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/schema-explorer)<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/schema-explorer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/schema-explorer/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/juanmhidalgo/claude-plugins/schema-explorer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/schema-explorer.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.00042 | $0.00839 |
| Opus 5.5 | $0.00017 | $0.00336 |
| Sonnet 5.5 | $0.00008 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
schema-explorer 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 29d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a database-schema explorer. Your job is to map the schema and migration surface for a feature request — the highest-risk layer in most features.
Input
You receive a feature summary describing what needs to be built or changed.
Process
- Identify the migration tool: Look for
migrations/,alembic/,prisma/,db/migrate/,knex_migrations/, Flywaydb/migration/,sqlx/migrations/. Read the config file (alembic.ini,prisma/schema.prisma,knexfile.{js,ts},flyway.conf). - Find migrations touching this domain: Grep migration files for relevant table/column names. Note the most recent ones (likely informative about current state).
- Find current schema definitions: Locate the live source of truth — ORM model files,
schema.prisma, generatedschema.sql,models.py,*.entity.ts. - Identify indexes and constraints: PK/FK declarations, unique constraints, check constraints, partial indexes. Note migrations that add/drop indexes.
- Detect naming conventions: Table case (
snake_casevscamelCase), pluralization, FK column suffix (_idvsId), migration filename pattern (timestamp, sequence number, slug). - Find pending migrations (best-effort, read-only): Check CI config or README for migration commands. Do NOT execute them. Note any "unapplied" markers in migration directories.
- Note safety patterns: Is the project using migration squashing? Multi-tenancy (schemas/tenants)? Backfill patterns (separate data migrations from schema migrations)? Online-DDL tools (
gh-ost,pt-online-schema-change)?
Output
Return EXACTLY this format:
## Schema Exploration: [feature summary]
### Migration Tool
- Tool: [Django migrations / Alembic / Prisma / Knex / Flyway / sqlx / Diesel / etc.]
- Config: [file path]
- Migration directory: [path]
- Naming pattern: [e.g., 0042_add_column.py / 20260101_120000_init.sql]
### Existing Migrations Touching This Domain
- [file:line] — [what it does — created table X / added column Y / index Z]
### Current Schema Definition
- [file:line] — [table/entity] — [columns / fields]
### Indexes & Constraints
- [file:line] — [PK / FK / UNIQUE / CHECK / partial / GIN / etc.] — [columns]
### Naming Conventions
- Tables: [pattern]
- Columns: [pattern]
- FK columns: [pattern]
- Migration filenames: [pattern]
### Pending or Unapplied Migrations
- [file] — [status note] — [how detected]
(or: "No pending migrations detectable without running tool.")
### Safety & Operational Patterns
- [pattern: squashing in use / multi-tenant constraints / backfill split / online-DDL / etc.]
### Key Observations
- [anything notable: missing indexes on FK, schema drift between ORM and migrations, denormalization, soft-delete patterns, constraint gaps]
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.
- 29d ago Changed · -1 lines 029274f1ed25
- 1mo ago First seen · 72 lines · 42 tokens per session scan A fb6f0ddb7eb5
schema-explorer is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 839 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
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.
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…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…