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 agentmods add skills/fmind/dot/dprintnpx skills add fmind/dot --skill dprintgit 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/dprint)<a href="https://agentmods.dev/skills/fmind/dot/dprint"><img src="https://agentmods.dev/badge/skills/fmind/dot/dprint.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00751 |
| Opus 5 | $0.00016 | $0.00376 |
| Sonnet 5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
dprint 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dprint
The formatter for configuration and markup files (JSON, Markdown, TOML, YAML); dprint formats only, linting lives in the language stacks (go-stack, python-stack, typescript-stack).
Configuration
dprint searches the current directory upward for dprint.json or dprint.jsonc and falls back to the global config (DPRINT_CONFIG_DIR) only when nothing is found, so every project needs its own resolvable config or it silently inherits whatever the global one contains.
- Copy (default): copy a known-good
dprint.jsoninto the project root; it is self-contained and version-pinned. The first run downloads uncached plugins; later runs use dprint's local cache. Bump plugin versions per repository. - Extends (DRY): set
"extends"to a single source of truth, a local path or a commit-pinned URL such as"https://raw.githubusercontent.com/fmind/dot/<commit>/dprint.json"; override rules or add plugins locally.
Commands
dprint fmt --allow-no-files # format:dprint — the hook appends {staged_files}; the flag keeps an empty list from exiting 14
dprint check # check:format — non-zero exit on drift
dprint add <plugin> # add and pin a plugin version
Mise Tasks
[tasks."format:dprint"]
description = "Format JSON, Markdown, TOML, YAML (dprint)"
run = "dprint fmt --allow-no-files" # mise appends the hook's {staged_files}
[tasks."check:format"]
description = "Check config and markup formatting (dprint)"
run = "dprint check"
Gotchas
- Plugin references: prefer the
npm:form (npm:@dprint/[email protected],npm:[email protected]) overhttps://plugins.dprint.dev/...wasmURLs; both resolve, and the npm form makes the current version onenpm view <plugin> versionaway. - Plugin order is precedence: the
pluginsarray order decides which plugin claims a file; keep specialized plugins before generic ones. - Embedded code blocks: the Markdown plugin formats fenced JSON, TOML, and YAML only when those plugins are loaded too.
- Staged vs whole-tree:
format:dprinttakes{staged_files}from the hook and restages fixes;check:formatalways runs on the whole tree.
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 · +1 lines abcb568f8a26
- yesterday First seen · 53 lines · 33 tokens per session scan A bbef5a3a2b97
dprint is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 751 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-09-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
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.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
cloud-run
Deploy container services to Google Cloud Run with Artifact Registry, keyless CI identity, Secret Manager, ko, or Dockerfiles.