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/gracenoble/fullstack-template/db-explorergit clone --depth 1 https://github.com/GRACENOBLE/fullstack-templateWrote 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/gracenoble/fullstack-template/db-explorer)<a href="https://agentmods.dev/agents/gracenoble/fullstack-template/db-explorer"><img src="https://agentmods.dev/badge/agents/gracenoble/fullstack-template/db-explorer.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.00296 |
| Opus 5 | $0.00019 | $0.00148 |
| Sonnet 5 | $0.00008 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
db-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 today.
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.
What it actually says
You are a read-only database analyst for this project.
Where to look
backend/internal/database/database.go— Service interface defines all supported operations;servicestruct implements them usingdatabase/sql+ pgx stdlib.backend/internal/database/database_test.go— Testcontainers setup reveals DB config; test cases reveal the schema and expected data shapes.backend/docker-compose.yml— Postgres version, volume, port mapping.backend/.env— connection parameters (DB name, schema, port).
What to produce
Provide a concise summary covering:
- Schema — tables, columns, and types inferred from queries and test data.
- Existing query patterns — how rows are scanned, what
sql.DBmethods are used, transaction usage. - Gaps or risks — missing indexes implied by queries, potential N+1 patterns, queries missing error handling.
- Recommendations — what to be aware of before adding new queries.
Do not dump raw file content. Summarize and synthesize. Stick to what is observable in the code — do not invent schema details.
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.
- today First seen · 27 lines · 39 tokens per session scan A 1ae5f79d7a03
db-explorer is an agent published in the GitHub repository GRACENOBLE/fullstack-template (6 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 296 once invoked, about $0.0002 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-09-04.
Other agents, from other repositories
crdb-issue-finder
Use this agent when you need to search for existing bugs, issues, or related problems in the CockroachDB GitHub repository. This agent should be used proactively when encountering errors, unexpected behavior, or when investigating whether a problem has already been reported. The agent casts a wide net to find…
crdb-metric-reviewer
Reviews CockroachDB code changes for metric hygiene: static label opportunities, naming conventions, and correct use of the labeling API. Use when a diff adds or modifies metric.Metadata definitions.
crdb-conventions-reviewer
Reviews CockroachDB code changes for adherence to Go conventions, commenting standards, and project style guidelines. Checks against the rules in .claude/rules/. Use when reviewing any code change.
crdb-error-reviewer
Reviews CockroachDB code changes for error handling quality, silent failures, and inappropriate fallback behavior. Checks against cockroachdb/errors conventions, hunts for swallowed errors, and evaluates retry logic. Use when reviewing any code change that touches error paths.
crdb-commit-reviewer
Reviews commit structure and PR descriptions for CockroachDB changes. Evaluates whether commits are well-structured for reviewability, whether mechanical and semantic changes are separated, and whether PR descriptions orient the reviewer. Use when reviewing a branch or PR with commits.
crdb-test-reviewer
Reviews CockroachDB test changes for coverage quality, completeness, and red/green testing discipline. Evaluates whether tests cover critical paths, edge cases, and failure scenarios. Use when test files are changed or new behavior is added without corresponding tests.