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 benchmarkgit 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/benchmark)<a href="https://agentmods.dev/skills/fmind/dot/benchmark"><img src="https://agentmods.dev/badge/skills/fmind/dot/benchmark/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/benchmark"><img src="https://agentmods.dev/badge/skills/fmind/dot/benchmark.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.00018 | $0.00392 |
| Opus 5.5 | $0.00007 | $0.00157 |
| Sonnet 5.5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
benchmark 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.
What it actually says
Benchmark
Produce comparable measurements for a stated performance question. Use hyperfine for commands, oha for simple HTTP load, and Locust for realistic concurrent user scenarios; diagnosing why something is slow belongs to systematic-debugging.
Workflow
- Confirm authority: never load-test a remote service you do not own or a production system without explicit approval; agree a load bound and stop condition appropriate to the target's capacity.
- Measure with the matching guide: read only that guide and its required resources; use at least 3 warmup runs and 10 measured runs for commands and at least 30 seconds for endpoints, and compare against a baseline measured the same way in the same session.
- Quantify uncertainty: compare repeated, equivalently controlled runs and report uncertainty in the difference; a run's standard deviation alone does not decide significance. Alternate baseline/candidate measurements when machine drift matters.
- Report: the command lines, the exported table, the relative change, and the conditions. Keep the raw export (
bench.json,oha.json, or Locust CSV) if the number will be tracked over time.
Task guides
- command-http: Compare command latency with hyperfine or measure HTTP throughput with oha.
- locust: Concurrent user scenarios, capacity tests, and acceptance thresholds.
What ships with it
2 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 52082a83417f
- 12d ago Changed · -2 lines b3c84dfd6ebf
- 14d ago Changed 832798365449
- 15d ago Changed · +5 lines · -4 tokens per session 6b2e0a6691f4
- 29d ago Changed 0ca3a18b95ab
- 1mo ago Changed · -20 lines · -16 tokens per session f783d792d2c6
- 1mo ago Changed · +1 lines df93ececb835
- 1mo ago Changed 4e37b613642c
- 1mo ago First seen · 48 lines · 38 tokens per session scan A 0fa47fc3ac52
benchmark is a skill published in the GitHub repository fmind/dot (12 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 392 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
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…
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.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
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.