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/supergoal-skillWrote 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/supergoal-skill/db-reader)<a href="https://agentmods.dev/agents/cskwork/supergoal-skill/db-reader"><img src="https://agentmods.dev/badge/agents/cskwork/supergoal-skill/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/supergoal-skill/db-reader"><img src="https://agentmods.dev/badge/agents/cskwork/supergoal-skill/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.00495 |
| Opus 5.5 | $0.00027 | $0.00198 |
| Sonnet 5.5 | $0.00013 | $0.00099 |
| Haiku 4.5 | $0.00007 | $0.00049 |
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 1mo 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.
This is a copy
97% identical to db-reader — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 31 lines · 67 tokens per session scan A ecca625af04a
db-reader is an agent published in the GitHub repository cskwork/supergoal-skill (5 stars, last pushed 9d ago), licensed MIT. It adds 67 tokens to every session and 495 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to db-reader, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
wiki-dev-eng-schema
Senior Fullstack Bun/TypeScript Engineer — Lane B (Schema, Ontology & Multi-vault) on the claude-wiki-pages development team. Owns ontology-profile-v1 (the predicate domain→range table and enum list), staleness derivation, the opt-in predicate range check, template/structural conformance, the multi-vault registry with…
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
plan-creation-qa-critic
QA / Critic for the plan-creation pipeline. Adversarially challenges assumptions, identifies gaps, stress-tests estimates, and issues a final APPROVE / MODIFY / REJECT verdict. Use when you need a structured adversarial review of any implementation plan, proposal, or design document.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.