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 dbhq-uk/dovetail-skill --skill dovetailgit clone --depth 1 https://github.com/dbhq-uk/dovetail-skillWrote 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/dbhq-uk/dovetail-skill/dovetail)<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.
<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>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.00102 | $0.03408 |
| Opus 5 | $0.00051 | $0.01704 |
| Sonnet 5 | $0.00020 | $0.00682 |
| Haiku 4.5 | $0.00010 | $0.00341 |
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.
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.
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 forstaleness/spec-flow/xref/convention, code forcode-hygiene - Pass the model override explicitly. Never let a reviewer inherit the orchestrator's model.
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.
- ci/dovetail-pr.yml 1.7 KB
- ci/dovetail-scheduled.yml 3.3 KB
- README.md 1.4 KB
- references/config.md 4.2 KB
- references/finding-schema.md 4.3 KB
- references/reviewers/claim-extract.md 1.8 KB
- references/reviewers/code-hygiene.md 1.4 KB
- references/reviewers/contradiction.md 2.3 KB
- references/reviewers/convention.md 1.4 KB
- references/reviewers/spec-flow.md 1.6 KB
- references/reviewers/staleness.md 1.5 KB
- references/reviewers/xref.md 1.3 KB
- scripts/bootstrap.py 6.0 KB runs code
- scripts/ci_dispatch.py 14 KB runs code
- scripts/claimscan.py 8.4 KB runs code
- scripts/classify.py 2.7 KB runs code
- scripts/cochange.py 8.3 KB runs code
- scripts/config.py 3.8 KB runs code
- scripts/convcheck.py 7.8 KB runs code
- scripts/discover.py 1.6 KB runs code
- scripts/dynref.py 7.1 KB runs code
- scripts/exactcheck.py 26 KB runs code
- scripts/gitmeta.py 4.3 KB runs code
- scripts/globmatch.py 1.7 KB runs code
- scripts/graphcheck.py 21 KB runs code
- scripts/issue.py 7.2 KB runs code
- scripts/plugins.py 4.5 KB runs code
- scripts/refgraph.py 13 KB runs code
- scripts/reviewer.py 10 KB runs code
- scripts/scan.py 9.0 KB runs code
- scripts/slugify.py 3.1 KB runs code
- scripts/store.py 3.1 KB runs code
- tests/test_bootstrap.py 4.7 KB runs code
- tests/test_claimscan.py 4.1 KB runs code
- tests/test_classify.py 2.7 KB runs code
- tests/test_cochange.py 5.2 KB runs code
- tests/test_config_plugins.py 6.0 KB runs code
- tests/test_convcheck.py 4.6 KB runs code
- tests/test_discover.py 3.9 KB runs code
- tests/test_dispatch_contract.py 11 KB runs code
- tests/test_end_to_end.py 8.9 KB runs code
- tests/test_exactcheck.py 11 KB runs code
- tests/test_gitmeta.py 6.6 KB runs code
- tests/test_globmatch.py 2.8 KB runs code
- tests/test_graphcheck_files.py 16 KB runs code
- tests/test_graphcheck_links.py 5.7 KB runs code
- tests/test_refgraph.py 20 KB runs code
- tests/test_reviewer.py 8.4 KB runs code
- tests/test_scan_github.py 4.9 KB runs code
- tests/test_scan_json.py 6.4 KB runs code
- tests/test_slugify.py 3.3 KB runs code
- tests/test_store.py 6.6 KB runs code
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.
- 9d ago First seen · 278 lines · 102 tokens per session scan A f20eb70127a9
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.
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.
one-way-door
Flags irreversible decisions before commit. Use for data models, infra, auth boundaries, API contracts, event schemas, CI/CD.
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…
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.
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".
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".