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/harness/harness-skills/dbops-changesetnpx skills add harness/harness-skills --skill dbops-changesetgit clone --depth 1 https://github.com/harness/harness-skillsWrote 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/harness/harness-skills/dbops-changeset)<a href="https://agentmods.dev/skills/harness/harness-skills/dbops-changeset"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/dbops-changeset.svg" alt="Measured on agentmods" 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.00078 | $0.07193 |
| Opus 5 | $0.00039 | $0.03596 |
| Sonnet 5 | $0.00016 | $0.01439 |
| Haiku 4.5 | $0.00008 | $0.00719 |
Grade A, and why
dbops-changeset 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- dbops-changeset — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 614 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DBOPS Changeset Generation
Generate Liquibase database changesets from natural language descriptions, anchored to a real schema and instance from the Harness DBOPS service.
When to Use
When the user asks to:
- Create, add, modify, or drop tables, columns, indexes, constraints, or views as Liquibase changeset operations
- Generate a database migration or changeset
- Fix a failed migration or update an existing changeset
- Apply schema changes as Liquibase YAML
Prerequisites
The Skill tool loads this file (SKILL.md) automatically — do not Read it again.
Before generating Liquibase YAML, Read reference.md using the exact path listed in
the Skill tool result. It contains all Liquibase YAML rules, change types, rollback
patterns, batch migration guidelines, MongoDB JSON string requirements, and the
clarifying questions policy. Apply those rules in Step 4 when generating the changeset.
Full Workflow
Step 0: Check for Pre-Seeded Context (ALWAYS do this first)
At conversation start, the initial message may contain a JSON block with pre-selected identifiers injected by the Harness frontend UI:
{
"dbops_schema_id": "users-schema",
"dbops_instance_id": "prod-instance"
}
Read this JSON block (if present) before doing any tool calls.
| What's in context | What to do |
|---|---|
dbops_schema_id + dbops_instance_id |
Skip Steps 1 AND 2 — but immediately fetch instance metadata via harness_get(resource_type="database_instance", resource_id="<dbops_instance_id>", dbschema_id="<dbops_schema_id>") to obtain connector (needed in Step 3) and check hasSnapshot (needed in Step 3-B). |
Only dbops_schema_id |
Skip Step 1 — use this schema ID. Then go to Step 2-A |
| Neither | Full Steps 1 and 2 |
What ships with it
1 file 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.
- 6d ago First seen · 614 lines · 78 tokens per session scan A 900dbc20a7d2
dbops-changeset is a skill published in the GitHub repository harness/harness-skills (103 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 7,193 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-30.
Other skills, from other repositories
bigquery-graph
Skill for Graph Query Language (GQL) or SQL/PGQ queries against a property graph. Includes path finding, multi-hop traversal, topological connection, shortest path, node reachability, edge connectivity, and semantic graph queries.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
migration-review
Review database migration files when a change adds or modifies paths under migrations/. Use it before merge to collect forward, rollback, locking, and data-safety evidence.