agentmods.dev

dot: Skill for Claude Code

.agents/skills/dot-verify/SKILL.md

dot-verify is a skill for Claude Code, Codex from fmind/dot. It costs 34 tokens per session (854 once invoked), scanned A, original, MIT.

A release-readiness workflow for the Dot project that reviews changes, checks documentation, runs project gates, and smoke-tests the command-line tool. A smoke test is a quick check that the main program works.

In plain words
What is it for?
Use it to inspect committed and uncommitted changes, verify repository documentation, run checks, and fix findings before a release.
Why use it?
It brings code, documentation, tests, and the working tree together before release, while preserving unrelated local work and avoiding commits or pushes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is fmind/dot's own configuration. It tells Claude Code and Codex how to work on dot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dot configures →

not rated 12repo changed 3d ago A scan 34 tokens original MIT
View source ↗ fmind/dot fmind.dev
Reuse

Borrowing it

Nothing to install: this file belongs to fmind/dot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/fmind/dot/main/.agents/skills/dot-verify/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/fmind/dot

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 dot-verify

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/fmind/dot/dot-verify"><img src="https://agentmods.dev/badge/skills/fmind/dot/dot-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 854 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.00034 $0.00854
Opus 5.5 $0.00014 $0.00342
Sonnet 5.5 $0.00007 $0.00171
Haiku 4.5 $0.00003 $0.00085

Measured 3d ago against content hash 8b0677f6790e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dot-verify 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 3d 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.

.agents/skills/dot-verify/SKILL.md · 31 lines

How it starts

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

Verify Dot

Prove that the current checkout (committed and uncommitted work) is correct, documented, and releasable. This skill sequences the owners; repository-review, repository-docs, dot-development, and dot-skills own the details. Verification fixes findings in place but never commits, pushes, or releases; dot-release owns that.

Workflow

  1. Record the baseline: record git status --short, staged and unstaged diffs, untracked files, and git fetch state against origin/main. Commits already on main since the last tag are part of the candidate; preserve unrelated work.
  2. Review the change set: list what changed since the last tag (git diff <tag>) plus uncommitted work, excluding generated locks. For large sets, fan out read-only reviews by area (dot Python, chezmoi and host config, docs and skills) and verify each finding against code or real local data before fixing. Behavior fixes need regression tests per dot-development.
  3. Synchronize docs: check README.md, AGENTS.md, dot_agents/AGENTS.md, .github/*.md, .agents/skills/, and skills/ against the code: removed or renamed files, commands and flags (uv run --frozen --project dot dot <command> --help), tasks (mise tasks), and JSON fields. Bump updated: on changed skills; run mise run format:skills for guide indexes; follow dot-skills for catalog changes.
  4. Run the gates: mise run all, then the host checks it omits: mise run check:completions and mise run test:starters. Rerun only what a later fix invalidates.
  5. Smoke-test the CLI from the repository root with uv run --frozen --project dot dot (--directory dot would resolve . to dot/): --help for every top-level command, then read-only commands: doctor, agent doctor, agent context --check, config show, status, orphan, cache, prune --dry-run, prune --aggressive --dry-run, pull --dry-run, trust --dry-run ., and agent stats --no-sync. Every exit code must be 0 or explained.
  6. Check the workstation when tools or dotfiles changed: mise run diff preview, dot orphan for retired targets (report, never delete), and mise run doctor. STALE for the installed dot is expected until release or mise run deploy.
  7. Report: fixed findings, deliberately left items with reasons, each check and its result, and confirm the tested snapshot equals the candidate (the working tree after the last fix).

Read the full file on GitHub · 31 lines

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. 3d ago Changed 8b0677f6790e
  2. 4d ago Changed · -1 lines 75a8f3c2c8c3
  3. 10d ago Changed bd7511b957ef
  4. 23d ago Changed 66c88bb93199
  5. 24d ago Changed a5d52a47164b
  6. 26d ago Changed 10709ee9adc3
  7. 1mo ago First seen · 32 lines · 34 tokens per session scan A f09af2357637

Subscribe to this mod's changes

dot-verify is a skill published in the GitHub repository fmind/dot (12 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 854 once invoked, about $0.0001 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-09-25.

Claude CodeGit and workflowReleasesTestingai-agentschezmoidotfilesfish-shellmise
Related

Other skills, from other repositories

release

Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.

fmind/dotfiles · 40 tokens

sync-release

Owns release-pipeline conventions: sr.yaml schema, the sr CLI verbs (init/plan/prepare/ release) and urmzd/sr action, typed publishers (cargo/npm/pypi/docker/go/custom), monorepo workspace discovery, versionfiles/stagefiles mapping, and post-release patterns. Language-specific build targets live in scaffold-rust…

urmzd/dotfiles · 136 tokens

setup-ci

Defines GitHub Actions workflow structure: ci.yml + release.yml naming, concurrency groups, bot-commit skip, workflowcall reuse, App-token checkout, and optional fsrc/teasr steps. Language-specific pipelines live in scaffold-rust, scaffold-go, scaffold-python, scaffold-node, scaffold-terraform. Use when setting up…

urmzd/dotfiles · 119 tokens

release-audit

Audit GitHub releases, git tags, and release assets for one repo or every repo in a directory. Flags orphaned tags, missing binaries/checksums, draft releases, floating tag drift, pre-release remnants, and (when sr.yaml is present) sr config issues. Read-only: never deletes or modifies tags/releases. Use when checking…

urmzd/dotfiles · 126 tokens

changelog

Audit, write, or update CHANGELOG.md following Keep a Changelog 1.1.0. Use when creating a CHANGELOG, or reviewing commits to ensure Unreleased reflects user-visible changes. Defers to auto-managed setups (changesets, release-please, git-cliff, semantic-release, towncrier) and applies semver 2.0.0 — or Haskell PVP for…

alunduil/alunduil-chezmoi · 89 tokens

mise

Configure pinned mise tools and canonical install, format, check, test, build, and watch tasks shared by hooks and CI.

fmind/dotfiles · 27 tokens