dovetail

dovetail is a skill for Claude Code from dbhq-uk/dovetail-skill. It costs 102 tokens per session (3,408 once invoked), scanned A, original, MIT.

A repository review skill that checks whether a project's files, documentation, code, and stated rules agree with one another. It separates certain results from reviewer judgments that may be uncertain.

In plain words
What is it for?
Use it to scan links, headings, unused files, duplicate content, code and documentation drift, contradictions, conventions, and signals from version-control history.
Why use it?
Repositories can accumulate broken references, outdated documentation, contradictions, duplicate content, and translations that no longer match the source. The skill helps examine these findings one at a time.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_SKILL_DIR} variable. Also seen: mentions subagents; names the AskUserQuestion tool.

Part of the dovetail plugin — 1 skill shipped together

Good fit Use it to scan links, headings, unused files, duplicate content, code and documentation drift, contradictions, conventions, and signals from version-control history.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dbhq-uk/dovetail-skill/dovetail
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 dbhq-uk/dovetail-skill --skill dovetail
Clone the repo
git clone --depth 1 https://github.com/dbhq-uk/dovetail-skill

Made for: Claude Code.

Or install dovetail, the plugin that ships this one along with the rest of its 1 skill.

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 dovetail

README.md
[![agentmods](https://agentmods.dev/badge/skills/dbhq-uk/dovetail-skill/dovetail/github.svg)](https://agentmods.dev/skills/dbhq-uk/dovetail-skill/dovetail)
Your own site
<a href="https://agentmods.dev/skills/dbhq-uk/dovetail-skill/dovetail"><img src="https://agentmods.dev/badge/skills/dbhq-uk/dovetail-skill/dovetail/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 dovetail

Your own site · 80×15
<a href="https://agentmods.dev/skills/dbhq-uk/dovetail-skill/dovetail"><img src="https://agentmods.dev/badge/skills/dbhq-uk/dovetail-skill/dovetail.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,408 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.
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.00102 $0.03408
Opus 5 $0.00051 $0.01704
Sonnet 5 $0.00020 $0.00682
Haiku 4.5 $0.00010 $0.00341

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

Security

Grade A, and why

dovetail 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 9d ago.

The scan reads SKILL.md. This mod also ships 40 executable files (scripts/bootstrap.py, scripts/ci_dispatch.py, scripts/claimscan.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.

skills/dovetail/SKILL.md · 278 lines

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.

dovetail

Checks whether a repository agrees with itself, and walks through what it finds.

Two layers produce findings. Exact findings are computed in Python - links, anchors, orphans, duplicates, flag and signature drift, conventions, git-history signals. They are certain. Judged findings come from reviewers - contradictions, semantic staleness, spec drift, non-Python dead code. They are probabilistic.

The user must always know which they are looking at. Never blur the two.

Run

1. Scan (always)

python3 ${CLAUDE_SKILL_DIR}/scripts/scan.py <repo-path> --format json

Seconds, no network, no model. Never modifies the target.

Read the JSON: findings, suppressed, counts, failed_checks, profile, file_count, edge_count.

If it exits 2, report the error and stop - the repository is not a git checkout, or .dovetail/config.toml is invalid. Do not proceed on defaults; a config the user wrote is one they expect to take effect.

2. Dispatch the judgement reviewers (unless the user said "quick" or "exact only")

Start these before triaging, so they land while the user works through the certain findings. Layer 1 finishes before the first reviewer returns, and a run abandoned after two minutes has still delivered every broken link and duplicate in the repository.

Get the clusters the contradiction reviewer needs:

python3 -c "import sys; sys.path.insert(0, '${CLAUDE_SKILL_DIR}/scripts'); \
from discover import discover; from refgraph import build_graph; from claimscan import build_clusters; \
import json; inv=discover('<repo-path>'); print(json.dumps(build_clusters(inv, build_graph('<repo-path>', inv))))"

Then spawn one subagent per reviewer, in parallel. For each:

  • Read its rubric from ${CLAUDE_SKILL_DIR}/references/reviewers/<name>.md
  • Read the contract from ${CLAUDE_SKILL_DIR}/references/finding-schema.md
  • Give it its context: clusters for contradiction, docs for staleness / spec-flow / xref / convention, code for code-hygiene
  • Pass the model override explicitly. Never let a reviewer inherit the orchestrator's model.

Read the full file on GitHub · 278 lines

Files

What ships with it

52 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. 9d ago First seen · 278 lines · 102 tokens per session scan A f20eb70127a9

Subscribe to this mod's changes

dovetail is a skill published in the GitHub repository dbhq-uk/dovetail-skill (3 stars, last pushed 23d ago), licensed MIT. It adds 102 tokens to every session and 3,408 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

review-work

Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.

code-yeongyu/oh-my-openagent · 63 tokens

one-way-door

Flags irreversible decisions before commit. Use for data models, infra, auth boundaries, API contracts, event schemas, CI/CD.

jamditis/claude-skills-journalism · 29 tokens

map-codebase

Deep architecture report that fans out parallel inspections across different aspects of the codebase (structure, tech stack, APIs, patterns, data flow, dependencies, testing) and synthesizes findings into a comprehensive document at .turbo/codebase-map.md and .turbo/codebase-map.html. Use when the user asks to "map…

tobihagemann/turbo · 106 tokens

critical-code-reviewer

Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.

posit-dev/skills · 67 tokens

reply-to-pr-threads

Draft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved threads are skipped, and posts via GraphQL. Use when the user asks to "reply to PR threads", "post PR thread replies", or "draft PR reply messages".

tobihagemann/turbo · 71 tokens

answer-reviewer-questions

For each reviewer question on a PR, recall implementation reasoning and compose a raw answer. Use when the user asks to "answer reviewer questions", "draft answers to PR questions", or "explain reviewer questions".

tobihagemann/turbo · 48 tokens