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/readme-agentsnpx skills add fmind/dot --skill readme-agentsgit 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/readme-agents)<a href="https://agentmods.dev/skills/fmind/dot/readme-agents"><img src="https://agentmods.dev/badge/skills/fmind/dot/readme-agents.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.00043 | $0.00468 |
| Opus 5 | $0.00022 | $0.00234 |
| Sonnet 5 | $0.00009 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
readme-agents 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 yesterday.
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
Sync README and AGENTS Files
Refresh AGENTS.md (tooling, commands, conventions, and layout for agents) and README.md (purpose, installation, and usage for humans) so both reflect the repository's current state. improve-docs owns the wider documentation set.
Workflow
- Research: scan the root directory and key config files (
pyproject.toml,go.mod,mise.toml,lefthook.yml) to identify tools and structure. - Update AGENTS.md: refresh the tool list and commands, and update the Layout section (a bullet list of top-level files and directories with a one-sentence purpose each).
- Update README.md: make purpose, prerequisites, and usage examples current and remove stale instructions.
- Validate: run
lychee README.md AGENTS.mdso refreshed links are proven live, not assumed.
Gotchas
- Separation of concerns: user-facing installation instructions belong in
README.md; technical conventions and rules belong inAGENTS.md. - Workflows become skills: a multi-step section that outgrows
AGENTS.mdmoves to a skill per skillify, leaving a one-line pointer.
Documentation
- AGENTS.md Open Standard · lychee
- Companion skills: agent-project (the initial
AGENTS.mdand layout), improve-docs (docs beyond these two files).
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.
- yesterday First seen · 32 lines · 43 tokens per session scan A fdbde2fa4bd7
readme-agents is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 468 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.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
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.
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.