dolt-database-version-control

dolt-database-version-control is a skill for Claude Code, Codex from Firstp1ck/pi-coding-agent-forge. It costs 53 tokens per session (1,801 once invoked), scanned A, original, MIT.

A workflow for Dolt, a SQL database with Git-like branches, commits, differences, merges, and history.

In plain words
What is it for?
Use it when designing or evaluating versioned database workflows, DoltHub collaboration, rollback plans, audit history, or versioned MySQL-compatible replicas.
Why use it?
It helps teams review, audit, compare, share, and roll back database changes instead of treating changing data as an untracked state.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when designing or evaluating versioned database workflows, DoltHub collaboration, rollback plans, audit history, or versioned MySQL-compatible replicas.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/firstp1ck/pi-coding-agent-forge/dolt-database-version-control
Install

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.

Any agent
npx skills add Firstp1ck/pi-coding-agent-forge --skill dolt-database-version-control
Clone the repo
git clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forge

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for dolt-database-version-control

README.md
[![agentmods](https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/dolt-database-version-control/github.svg)](https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/dolt-database-version-control)
Your own site
<a href="https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/dolt-database-version-control"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/dolt-database-version-control/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.

agentmods 80×15 button for dolt-database-version-control

Your own site · 80×15
<a href="https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/dolt-database-version-control"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/dolt-database-version-control.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,801 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.01801
Opus 5.5 $0.00021 $0.00720
Sonnet 5.5 $0.00011 $0.00360
Haiku 4.5 $0.00005 $0.00180

Measured 1mo ago against content hash 43edecacd4bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dolt-database-version-control 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.

The scan reads SKILL.md. This mod also ships 1 executable file (tests/test_contract.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

pi-skill-dolt-database-version-control/skills/dolt-database-version-control/SKILL.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dolt Database Version Control

Use this skill to decide how, when, why, and where to use Dolt, and to produce safe adoption plans for Dolt-backed systems.

When to use

Use this skill when the user asks about any of the following:

  • Dolt, DoltHub, Hosted Dolt, DoltLab, DoltgreSQL/Doltgres, or "Git for data".
  • Version-controlling relational data with branches, commits, diffs, merges, remotes, or pull-request-like workflows.
  • Adding audit history, rollback, review-before-publish, or branch-per-user changes to an application database.
  • Creating a versioned MySQL or MariaDB replica for queryable history, disaster recovery, debugging, or change-data-capture-like workflows.
  • Comparing Dolt against Git+CSV, temporal tables, soft deletes, slowly changing dimensions, CDC pipelines, event sourcing, plain MySQL, or Postgres.
  • Designing commands, SQL procedures, or rollout checks for a Dolt proof of concept.

Do not use this skill for generic Git, generic SQL, or generic MySQL/Postgres administration unless Dolt or database version control is materially involved.

Inputs and assumptions

Before recommending Dolt, identify:

  • The current database engine, SQL dialect, schema size, write/read throughput, data sensitivity, and deployment topology.
  • Whether the goal is application-primary storage, collaborative dataset management, audit/disaster recovery, local agent memory, or a versioned replica beside an existing database.
  • Whether MySQL-compatible clients are acceptable. If Postgres compatibility is mandatory, treat Doltgres/DoltgreSQL as a separate maturity decision and verify current status from official sources.
  • Whether immutable history conflicts with retention, privacy, right-to-erasure, or secret-handling requirements.
  • Whether users need branch/merge conflict resolution and who will review or resolve conflicts.

Use references/dolt-guide.md as the packaged baseline. For current versions, installation commands, hosted offerings, maturity labels, or production claims, verify against official Dolt docs or the DoltHub GitHub repositories before finalizing.

Read the full file on GitHub · 127 lines

Files

What ships with it

2 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.

Changes

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.

  1. 1mo ago First seen · 127 lines · 53 tokens per session scan A 43edecacd4bc

Subscribe to this mod's changes

dolt-database-version-control is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (91 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,801 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

git-query-tools

Two workspace tools for structured data queries.

rcarmo/piclaw-addons · 21 tokens

convex-component-authoring

How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.

waynesutton/convexskills · 28 tokens

publish-npm-version

Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…

prisma/orm · 182 tokens

triage-contributor-pr

Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…

prisma/orm · 131 tokens

contrib-pr

Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.

prisma/orm · 65 tokens

db-load-git

A command for loading configuration files changed in Git into a 1C database. Git is a system that records file changes and versions.

Nikolay-Shirokov/cc-1c-skills · 43 tokens