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 skills/drhalto/agentmako/mako-databasenpx skills add drhalto/agentmako --skill mako-databasegit clone --depth 1 https://github.com/drhalto/agentmakoWhat 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.00053 | $0.00663 |
| Opus 5 | $0.00026 | $0.00331 |
| Sonnet 5 | $0.00011 | $0.00133 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
mako-database 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 3d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mako Database
Use this skill for direct database introspection. These tools require the project to have a live DB binding configured. If the user asks how app code uses database objects, use trace or neighborhood tools instead.
Tools
db_ping
Use to verify database connectivity and project wiring.
- Best when DB tools seem unavailable or the user asks whether the DB is connected.
- Use before deeper DB queries when the binding is uncertain.
db_columns
Use to inspect columns and primary-key details for one or more tables.
- Best for narrow column questions.
- Use
db_table_schemawhen indexes, constraints, triggers, or broader table shape matter.
db_fk
Use to inspect foreign keys and relationships.
- Best for inbound/outbound relationship questions.
- Pair with
table_neighborhoodwhen code readers/writers also matter.
db_rls
Use to inspect row-level security status and policies.
- Best for policy and protection questions.
- Pair with
tenant_leak_auditfor broader tenant-boundary risk review.
db_rpc
Use to inspect database RPC/function definitions, signatures, args, return shape, language, and security.
- Pair with
rpc_neighborhoodortrace_rpcwhen app-code callers matter.
db_table_schema
Use to inspect the full table shape, including columns, indexes, constraints, foreign keys, RLS, and triggers.
- Use when column-only output is insufficient.
- Pair with
trace_tableortable_neighborhoodwhen code usage matters.
Feedback Logging
Log agent_feedback when a DB introspection result here was notably
useful, partial, noisy, stale, wrong, or wasted the turn. Skip routine
calls.
Required procedure (see /mako-ai:mako-guide for full rules and
reason-code vocabulary):
- Call
recall_tool_runsto get the prior run'srequestId. Do not fabricate one — if no run is recalled, skip feedback. - Call
agent_feedbackwithreferencedToolName,referencedRequestId,grade: "full" | "partial" | "no",reasonCodesfrom the starter vocabulary in/mako-ai:mako-guide, and a shortreason.
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.
- 3d ago First seen · 88 lines · 53 tokens per session scan A 3621b86e7086
mako-database is a skill published in the GitHub repository drhalto/agentmako (51 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 663 once invoked, about $0.0003 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 skills, from other repositories
ctxo-safe-edit
Use BEFORE editing, renaming, or deleting any function, class, or method, to avoid breaking dependents.
ctxo-understand
Use at the START of any code task (fix, extend, refactor, understand) before reading source files, to orient with ctxo and avoid going in the wrong direction.
ctxo-review-pr
Use when reviewing a PR, a diff, or recent changes, to get a full risk assessment in one call.
db-check
Validate database schema integrity and check for common issues.
db-context-postgres
Validate that a generic Postgres database (GCP Cloud SQL, GKE Autopilot, self-hosted, etc.) is reachable via psql or pgdump, introspect a user-scoped subset of the schema (extensions, tables, columns, indexes, foreign keys, and optionally RLS policies and functions), and persist the result as DBCONTEXT.md inside the…
db-context-supabase
Validate that a Supabase MCP server is reachable, introspect a user-scoped subset of the database (tables, columns, types, RLS policies, optionally functions and recent migrations), and persist the result as DBCONTEXT.md inside the active task folder; adds a single ## DB context cross-link in SOURCEOFTRUTH.md.…