dolt-mcp-vcs

dolt-mcp-vcs is a skill for Claude Code from jeremylongshore/dolt-mcp-vcs-plugin. It costs 252 tokens per session (3,197 once invoked), scanned A, original, Apache-2.0.

A version-control workflow for Dolt, a database with Git-like branching and history, including DoltHub and beads task-tracker backends.

In plain words
What is it for?
It is for checking Dolt connections, working with beads data, publishing to DoltHub, and troubleshooting Dolt and bd failures.
Why use it?
It helps diagnose issues such as missing DoltHub remotes, failed pushes, and delayed JSONL exports. It first identifies which Dolt setup the project is using.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the dolt-mcp-vcs plugin — 1 skill, 5 agents, 1 MCP server shipped together

Good fit It is for checking Dolt connections, working with beads data, publishing to DoltHub, and troubleshooting Dolt and bd failures.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add jeremylongshore/dolt-mcp-vcs-plugin
Claude Code
/plugin install dolt-mcp-vcs

Made for: Claude Code.

Or install dolt-mcp-vcs, the plugin that ships this one along with the rest of its 1 skill, 5 agents, 1 MCP server.

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-mcp-vcs

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeremylongshore/dolt-mcp-vcs-plugin/dolt-mcp-vcs/github.svg)](https://agentmods.dev/skills/jeremylongshore/dolt-mcp-vcs-plugin/dolt-mcp-vcs)
Your own site
<a href="https://agentmods.dev/skills/jeremylongshore/dolt-mcp-vcs-plugin/dolt-mcp-vcs"><img src="https://agentmods.dev/badge/skills/jeremylongshore/dolt-mcp-vcs-plugin/dolt-mcp-vcs/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-mcp-vcs

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeremylongshore/dolt-mcp-vcs-plugin/dolt-mcp-vcs"><img src="https://agentmods.dev/badge/skills/jeremylongshore/dolt-mcp-vcs-plugin/dolt-mcp-vcs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 252 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,197 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.00252 $0.03197
Opus 5 $0.00126 $0.01598
Sonnet 5 $0.00050 $0.00639
Haiku 4.5 $0.00025 $0.00320

Measured 12d ago against content hash 88b64b4ac219, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

dolt-mcp-vcs scanned grade A with 1 finding 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 12d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Bash(curl:*)
skills/dolt-mcp-vcs/SKILL.md · 185 lines

How it starts

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

dolt-mcp-vcs

One skill for every make and model of Dolt: detect the flavor and mode first, then do version-control work over the beads (bd) backend and DoltHub.

Formerly beads-dolt — same plugin, renamed to its Dolt-first identity. The beads-dolt install slug still resolves (a deprecated catalog alias) and /beads-dolt is still an accepted trigger, so existing installs keep working — beads is now use-case adapter #1, not the whole skill.

The Dolt and DoltHub-aware layer for the beads (bd) task tracker. It composes with — does not replace — the global beads skill: that skill runs the bead work cycle; this one handles the Dolt backend, DoltHub visibility, and the bd plus Dolt failure modes.

Overview

bd stores every issue in a version-controlled Dolt database. Two things bite teams repeatedly:

  1. "My beads aren't showing in DoltHub." The overwhelmingly common cause is that the workspace's Dolt repo has no remote configured — so nothing is ever pushed. A file-protocol or GitHub backup does not make beads appear on DoltHub; only a Dolt remote plus a push does.
  2. JSONL appears stale after rapid writes. This is the export throttle, not data loss. As of bd 1.0.4 the historical rapid-write race (failure mode 6) is fixed at the SQL-transaction level; the database is always correct, only the issues.jsonl file can lag.

This skill diagnoses both, applies the fixes, and routes deeper work to five bundled agents. It keeps no frozen copy of bd/Dolt internals — a baked snapshot goes stale the moment upstream ships a release; the installed binary wins on any conflict. Verify version-specific behavior live (bd --help, bd <cmd> --help, bd dolt show) and consult the upstream docs; Read references/dolt-internals.md for the directory of those authoritative sources. The agents fetch current truth in their own context, so answers track the installed binary rather than a guess.

Read the full file on GitHub · 185 lines

Files

What ships with it

4 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. 12d ago First seen · 185 lines · 252 tokens per session scan A 88b64b4ac219

Subscribe to this mod's changes

dolt-mcp-vcs is a skill published in the GitHub repository jeremylongshore/dolt-mcp-vcs-plugin (4 stars, last pushed 17d ago), licensed Apache-2.0. It adds 252 tokens to every session and 3,197 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

document-release

Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ensure all project documentation accurately reflects shipped code. Covers README, ARCHITECTURE, CONTRIBUTING, CHANGELOG…

DollarDill/beads-superpowers · 103 tokens

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.

DollarDill/beads-superpowers · 44 tokens

init

Initialize, reindex, or manage the git-pkgs dependency database. Use when setting up git-pkgs in a repository for the first time, updating the database after pulling new commits, or checking database status.

git-pkgs/skills · 44 tokens

project-init

Use when beads/Dolt database initialization fails, when bd commands return errors about missing databases, when setting up beads in a new project, or when recovering from diverged Dolt history. Handles fresh init, bootstrap from remote, and recovery workflows.

DollarDill/beads-superpowers · 52 tokens

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/orm · 48 tokens

review-implement-phase

Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.

prisma/orm · 38 tokens