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 skills add d-o-hub/github-template-ai-agents --skill database-devopsgit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/skills/d-o-hub/github-template-ai-agents/database-devops)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/database-devops"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/database-devops/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/skills/d-o-hub/github-template-ai-agents/database-devops"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/database-devops.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.00074 | $0.01867 |
| Opus 5.5 | $0.00030 | $0.00747 |
| Sonnet 5.5 | $0.00015 | $0.00373 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade A, and why
database-devops 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.
How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database & DevOps
Database lifecycle management with DevOps practices for safe schema evolution, query optimization, and multi-database orchestration.
When to Use
- Schema design - New database schema design and normalization
- Migration planning - Safe schema evolution with data transformations
- Naming conventions - Consistent naming for tables, columns, and migration files
- Query optimization - Index recommendations, query rewriting, performance tuning
- Multi-database orchestration - Cross-database transactions, data sync
- Infrastructure-as-Code - Terraform/Pulumi database provisioning
- Backup/Recovery - Automated backup strategies and disaster recovery
Core Workflow
Schema Design Phase
- Requirements gathering - Data entities, relationships, access patterns
- Conceptual design - ERD, entity relationships, cardinality
- Logical design - Table structures, column types, constraints
- Physical design - Indexing, partitioning, storage considerations
- Normalization review - 3NF/BCNF compliance vs. denormalization needs
Naming Conventions
- Migration files -
YYYYMMDD_description.sql(timestamp-prefixed, one concern per file) - Tables - snake_case, plural (e.g.,
resources,permissions) - Columns - snake_case (e.g.,
resource_id,created_at)
Migration Planning Phase
- Analyze current schema - Existing tables, constraints, indexes
- Define target state - Desired schema changes
- Plan migration steps - Ordered, idempotent operations
- Assess data impact - Data transformations needed
- Design rollback - Reversible operations where possible
- Apply naming conventions - Verify migration file names and schema follow naming standards
Execution Phase
- Test in staging - Run migrations against production-like data
- Backup data - Full backup before destructive changes
- Execute migration - Apply changes with monitoring
- Verify integrity - Check constraints, data consistency
- Update applications - Deploy code changes
- Log migration - Record migration in migration history table for tracking and rollback
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 5.3 KB
- evals/files/migrations/20260101_add_settings.sql 948 B
- evals/files/migrations/20260215_update_schema.sql 339 B
- evals/files/migrations/20260301_add_orders_index.sql 276 B
- references/backup-strategies.md 13 KB
- references/iac-examples.md 16 KB
- references/migration-patterns.md 8.5 KB
- references/query-optimization.md 9.7 KB
- references/rollback-strategies.md 305 B
- references/schema-patterns.md 8.7 KB
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 · 250 lines · 74 tokens per session scan A 2b539002b345
database-devops is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 1,867 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-08-31.
Other skills, from other repositories
omh-relational-db
This is an OMH relational-db workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
redteam-sqli-detail-pack
Domain routing and boundary guidance for authorized SQL injection testing, including union-based, blind, error-based, stacked query, and second-order SQL injection variants. Use when a task belongs to the SQL injection domain and needs scope, evidence, pivot, or exit criteria.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
data-governance
Use this skill when designing or reviewing data governance: schema ownership, PII handling, retention, lineage, access policy, and migration safety for services and data stores. Triggers: user says "data governance", "PII", "schema ownership", "retention policy", "data lineage", "migration safety".
backup-recovery
Design and verify backups and restoration for owned databases, files and application state. Use when preparing recovery, migrating data or testing backups; protect the source and prove restore into an isolated destination before calling recovery ready.