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/d-o-hub/github-template-ai-agents/database-devopsnpx skills add d-o-hub/github-template-ai-agents --skill database-devopsgit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWhat 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.00074 | $0.01867 |
| Opus 5 | $0.00037 | $0.00933 |
| Sonnet 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 yesterday.
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
7 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.
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.
- yesterday 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.0004 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.