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 flurdy/agent-skills --skill beads-migrate-to-doltgit clone --depth 1 https://github.com/flurdy/agent-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/flurdy/agent-skills/beads-migrate-to-dolt)<a href="https://agentmods.dev/skills/flurdy/agent-skills/beads-migrate-to-dolt"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/beads-migrate-to-dolt/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/flurdy/agent-skills/beads-migrate-to-dolt"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/beads-migrate-to-dolt.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.00039 | $0.03309 |
| Opus 5 | $0.00019 | $0.01655 |
| Sonnet 5 | $0.00008 | $0.00662 |
| Haiku 4.5 | $0.00004 | $0.00331 |
Grade A, and why
beads-migrate-to-dolt 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 today.
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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beads Storage and Schema Migration
Own data preservation, conversion/schema upgrade, verification, and coordinated publication for one explicitly selected repository. Do not install or upgrade tools during the run. Reading this skill or editing it is not permission to migrate a database.
Usage
/beads-migrate-to-dolt [repository-path]
/beads-migrate-to-dolt --aftercare [repository-path]
Default mode runs the core steps below. --aftercare selects only the
confirmed aftercare procedure, not another migration.
Never enter aftercare automatically at the end of migration. Reject unknown/duplicate flags.
Read version and capability evidence before either mode. It records
checked CLI help, not universal compatibility. Read --help before each version-sensitive command;
missing capabilities are a blocker, not permission to guess a flag or change the installed version.
1. Bind the target without opening a store
Read the repository's own rules and the Beads baseline. At a workspace root,
use ~/.agents/skills/next/scripts/next-select stores for file-only repository discovery. Select
exactly one explicit absolute repository path as ROOT, matching its physical .beads location.
If selection is ambiguous, ask; never infer the target from an ID prefix or migrate every member.
Do not resolve a Bead ID before backup: the resolver's issue probes open databases. Resolve any
later tracker reads normally, after protection; they are not migration target discovery.
Inspect local files without opening the engine. Record only redaction-safe storage mode/path,
configured remote identity, and policy values; never dump full config or credential values.
Account for redirected or external storage, Git common directories, symlinks, shared servers,
and legacy worktree JSONL. A .beads copy alone cannot protect an external database.
issues.jsonl alone does not establish which backend is authoritative. No installation means stop,
not automatic bd init. Partial/unknown evidence is not permission to rebuild a store.
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.
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.
- today Changed · -478 lines · +5 tokens per session scan C → A f1921f63d5d2
- 12d ago First seen · 756 lines · 34 tokens per session scan C b4bd56d917a7
beads-migrate-to-dolt is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 3,309 once invoked, about $0.0002 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
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.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.