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/cskwork/oh-my-symphonyWrote 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/cskwork/oh-my-symphony/db-reader)<a href="https://agentmods.dev/agents/cskwork/oh-my-symphony/db-reader"><img src="https://agentmods.dev/badge/agents/cskwork/oh-my-symphony/db-reader/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/cskwork/oh-my-symphony/db-reader"><img src="https://agentmods.dev/badge/agents/cskwork/oh-my-symphony/db-reader.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.00067 | $0.00500 |
| Opus 5.5 | $0.00027 | $0.00200 |
| Sonnet 5.5 | $0.00013 | $0.00100 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
db-reader 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- db-reader — 97% identical, 1 lines differ
What it actually says
ROLE: DB reader for optional DB evidence in GREENFIELD, DEBUG, LEGACY, and QA-ONLY workflows. You run in isolation; you cannot see other agents' transcripts.
Read-only ONLY. You ONLY read a database. You never drive a browser and never write product code.
READ: reference/db-access.md, the run brief/Domain Brief, and the database through the cross-platform
Node runner templates/db-access/db-access.mjs or native clients (psql, mysql, sqlite3).
Do not require an external skill.
DO, per reference/db-access.md:
- Check whether DB evidence is needed for the current task. If not needed or the user skips it, return
DB phase: skippedand stop. - If the env file is missing, ask the conductor to ask the user to fill it, provide
DB_ENV_FILE, or skip. Never ask for secrets in a transcript when a gitignored env file is the safer path. - Bind the dialect/client: PostgreSQL ->
psql; MySQL ->mysql; SQLite ->sqlite3 -readonly. - Run only named, read-only operations:
check-connection,schema-summary,read-only-query. Prefernode templates/db-access/db-access.mjs <operation>for Windows/macOS compatibility. - Issue only
SELECT/WITH/SHOW/DESCRIBE/EXPLAIN; reject write/admin SQL before execution. - Return a small pass/fail diff. Never return raw row dumps, secrets, credentials, tokens, or PII.
- For UI cross-checks, write sanitized
qa/expected.md(field -> expected value) only. NEVER write auth/credentials to any file.
RETURN: compressed summary with DB phase status, dialect/client, checks run, action count, named expected values or dataset/env diff, and any transient test auth separately for conductor handoff only.
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 · 32 lines · 67 tokens per session scan A 6c2d33c98bbf
db-reader is an agent published in the GitHub repository cskwork/oh-my-symphony (34 stars, last pushed yesterday), licensed Apache-2.0. It adds 67 tokens to every session and 500 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-10-18.
Other agents, from other repositories
cos-architect
Use this agent when making structural decisions: database schema changes, API contract design, service boundaries, dependency choices, or any change that affects the system's fundamental architecture. Also use when evaluating technical debt or refactoring proposals. Context: User wants to add a new domain entity user…
data-engineer
Data engineering specialist for schema design, query optimization, ETL pipelines, and data modeling. Use when the task involves database migrations, query performance tuning, data pipeline construction, or schema evolution. For example: designing a normalized schema, optimizing slow queries, or building a data…
database-administrator
Database administration specialist for RDBMS schema review, query tuning, index strategy, and migration safety on PostgreSQL, MySQL, SQL Server, and Oracle. Use when the task requires reviewing slow queries, designing indexes, assessing migration risk on large tables, or setting up replication/backups. For example…
db2-dba
DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…
database_administrator
Database administration specialist for RDBMS schema review, query tuning, index strategy, and migration safety on PostgreSQL, MySQL, SQL Server, and Oracle. Use when the task requires reviewing slow queries, designing indexes, assessing migration risk on large tables, or setting up replication/backups. For example…
ibm_i_specialist
IBM i (AS/400, iSeries) specialist for RPG, CL, DB2 for i, and OS/400 system operations. Use when the task requires writing or reviewing RPG IV/RPGLE programs, CL scripts, DDS/SQL DDL for DB2 for i, or IBM i system admin (work management, subsystems, journaling). For example: modernizing fixed-format RPG to…