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 fmind/dot --skill dot-cligit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/dot-cli)<a href="https://agentmods.dev/skills/fmind/dot/dot-cli"><img src="https://agentmods.dev/badge/skills/fmind/dot/dot-cli/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/fmind/dot/dot-cli"><img src="https://agentmods.dev/badge/skills/fmind/dot/dot-cli.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.00036 | $0.00713 |
| Opus 5.5 | $0.00014 | $0.00285 |
| Sonnet 5.5 | $0.00007 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
dot-cli 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dot CLI
Use dot for bounded repository operations, local diagnostics, and agent-session archives. The installed command and its --help own the active interface. Dot also owns workstation login, setup, and cache workflows; native CLIs retain credentials and provider behavior.
Workflow
- Run documented commands directly: read the relevant
--helponly for an unfamiliar subcommand or after a usage error. Global options precede subcommands. - Select the operation's guide; previews authorize nothing: choose the guide for the requested operation; diagnostics and previews do not authorize login, cleanup, publication, or remote writes.
- Verify results at the requested level: local checks and hosted outcomes are separate evidence.
Task guides
- authentication: Inspect and apply configured provider login, OAuth scopes, and account policy.
- context: Measure discovery and instruction budgets in source or installed skill catalogs.
- contracts: Resolve configuration, JSON output, exit codes, and session archive compatibility.
- daily-workflows: Run repository status and pull, folder trust, session sync and statistics, cleanup, and Fish completions.
- disk-space: Audit workstation disk headroom, cache growth and shared tool versions before large downloads or builds.
- operations: Inspect repositories, diagnose workstation health, and manage session archives with dot.
- orphans: Find files chezmoi deployed but no longer manages, then decide per path whether to keep, remove, or forget them.
Workflow ownership
Use conventional-commit for staged commits, github-pull-request for PRs, and repository mise tasks for releases. Use dot login and dot setup for configured provider policy (authentication); inspect gh auth, gcloud auth, and gws auth directly for native diagnostics, and use auth-status for a read-only login and expiry sweep. Skills own AI judgment; deterministic privacy and mutation boundaries still apply.
What ships with it
7 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 5c49e1443a0d
- yesterday Changed 6c591a6de558
- 7d ago Changed db3e2f23c1f7
- 10d ago Changed 939221d978ef
- 12d ago Changed · +9 tokens per session 4361b6b477fa
- 14d ago Changed 812babdb271f
- 15d ago Changed · -1 lines · +6 tokens per session 8db58e611aad
- 17d ago Changed 4e1434532d2f
- 20d ago Changed 74ee1a3082b7
- 23d ago First seen · 47 lines · 21 tokens per session scan A f14b13713011
dot-cli is a skill published in the GitHub repository fmind/dot (12 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 713 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-03.
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.
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…
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…
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…
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…
github-repository
Configure a GitHub repository's metadata (description, homepage, topics) and solo-developer settings via gh, derived from the codebase. Use when setting up or tidying a repo's GitHub settings.