dotfiles
AGENTS.md13 starsChanged 3 days agoMITView on GitHub
This is fmind/dot — chezmoi + mise dotfiles for AI-CLI-first, Python-first development on Linux and macOS. Setup, usage, and common tasks live in README.md. See common tasks; mise tasks lists all tasks and aliases (mise run <task>, or `~/.local/b
1 other project uses a version of this.
Adopted by
Most recently taken up by
- fmind/dotword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- fmind/dot★ 13100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,843 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository67 other files it gives its agents.
- dot_agents/AGENTS.mdAGENTS.md
- skills/repository-docs/references/agents.mdAGENTS.md
- chezmoiSkill
- dot-developmentSkill
- dot-releaseSkill
- dot-skillsSkill
- dot-verifySkill
- acliSkill
- agent-evaluationSkill
- agent-frameworksSkill
- agent-harnessesSkill
- agent-projectSkill
- agent-protocolsSkill
- agySkill
- airflowSkill
- auth-statusSkill
- awsSkill
- bfSkill
- chrome-devtoolsSkill
- clipboardSkill
- cloud-runSkill
- code-securitySkill
- colabSkill
- databricksSkill
- diagrams-as-codeSkill
- dockerSkill
- documentation-siteSkill
- dot-cliSkill
- dprintSkill
- draft-docSkill
- draft-mailSkill
- duckdbSkill
- fmind-visualsSkill
- full-reviewSkill
- gcloudSkill
- ghSkill
- git-deliverySkill
- github-actionsSkill
- github-issuesSkill
- github-pull-requestSkill
- github-repositorySkill
- google-developerSkill
- gwsSkill
- hfSkill
- infra-as-codeSkill
- kaggleSkill
- kubernetesSkill
- lesson-learnedSkill
- mcp-setupSkill
- miseSkill
- model-providersSkill
- playwrightSkill
- project-scaffoldingSkill
- python-mlopsSkill
- python-stackSkill
- python-webSkill
- repository-docsSkill
- scheduled-jobsSkill
- skillifySkill
- <name>Skill
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Parallelize independent CLI probes: use run_parallel (fmind_dot.process) for independent subprocess, repository, and tool checks so dot …
- Distinctive: line 15
Keep README for users; workflows go in skills: keep setup, auth, everyday usage, and the short task table in README.md.
- Very specific: line 24
CLI (
dot) & workstation: follow dot-development for implementation, tests, and installation proof, dot-cli for dot login, setup, cache, …
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md (Project)
This is fmind/dot — chezmoi + mise dotfiles for AI-CLI-first, Python-first development on Linux and macOS. Setup, usage, and common tasks live in README.md.
House rules
- Edit chezmoi sources, never deployed copies: change this repository, not files under
$HOME; automation runschezmoi apply --force. Naming, templates, and secrets: chezmoi skill. - Treat this repository as public — never leak information: Never put customer or employer names, domains, emails, project or account IDs, repo or service names, hostnames, local paths, or details from untracked configs (
~/.config/dot.yaml,~/.config/git/config.*). Use only synthetic fixtures onfmind.dev,fmind.ai, or RFC 2606 domains (@example.com,@example.test). - Never commit decrypted secrets:
*.agefiles stay encrypted; never write plaintext secrets to the source tree, diffs, logs, or command arguments. Native credentials are create-only seeds; scoped keys usedot secret runand preserve account overrides (Secret Management). - Match validation to the task: read-only reviews need only evidence checks; doc and instruction edits need formatting, link, and contract checks (
mise run check:skills); behavior changes need focused pytest runs and affected static checks.mise run doctorchecks local workstation health (dot, chezmoi, and mise);mise run check,test, andallvalidate the repository (allruns whole-tree gates without rewriting files, whilemise run formatwrites the tree — isolate formatting when unrelated edits are present; runallfor cross-cutting changes, dependencies, packaging, releases, or full qualification). Reuse passing results while inputs remain unchanged. - Parallelize independent CLI probes: use
run_parallel(fmind_dot.process) for independent subprocess, repository, and tool checks sodotstays synchronous while bounding concurrent I/O and preserving deterministic output order. - Never use sudo: stay user-space; install via
mise. - Choose global tools for agent coding:
dot_config/mise/config.tomlserves AI-agent coding (harnesses, service connectors, and cross-project CLIs agents run), plus a few human review/shell tools (LazyVim, lazygit, lazydocker, the macOS Docker stack, Fish, Zellij). Pin project tools in their project; keep one global only when it must work outside projects (such as formatters and linters LazyVim runs on any file) and state why in its comment; a global copy never replaces a project pin. - Lock tools with mise, never edit generated locks: use mise lockfile revision 4 and keep
dot_config/mise/mise.lockwith its referencedlocks/dependency graphs; never hand-edit or format generated locks.mise run lockresolves the portable baseline in isolation, andmise run lock:tool TOOL...bumps only the named global tools (clear a stalemise latest TOOLwithmise cache clearfirst);mise run fullinstalls with--locked; Python dependencies lock indot/uv.lock. - Keep README for users; workflows go in skills: keep setup, auth, everyday usage, and the short task table in
README.md; put contributor workflows in skills and sync docs via repository-docs. - Pin themes and terminal defaults: fmind/theme owns the palette, native app files, and
~/.agents/DESIGN.md. Fetch standalone themes via.chezmoiexternal.toml.tmplpinned to one commit with SHA-256 checksums (mise run upgradeadvances the pin); when tools require merged styles, copy only the native theme block with an upstream source comment. Terminal tools follow the Ghostty ANSI palette, inherit GoogleSansCode Nerd Font Mono from Ghostty, and enable Vim mode in every TUI that supports it.
Workflows
See common tasks; mise tasks lists all tasks and aliases (mise run <task>, or ~/.local/bin/mise if not in $PATH; running from dot/ resolves to the root tasks).
- Iterate: edit source → run focused checks →
mise run diff→mise run applywhen deployment is in scope (runs eligible hooks and writes managed files). Lefthook runs commit/push checks; CI runs the full gate. - Add or upgrade tools: for project pins see mise; for global tools insert into
[tools]indot_config/mise/config.tomlalphabetically within its group (backend-prefixed entries, registry names, then per-platform tables) →mise run lock→mise run full.mise run upgradeupgrades this workstation's dependencies, tools, theme pin, and plugins only; upgrade other repos separately per upgrade-tools. - CLI (
dot) & workstation: follow dot-development for implementation, tests, and installation proof, dot-cli fordot login,setup,cache,prune, and workspace commands (explicit commands, never apply hooks), and agent usage for usage reports. - Completions:
mise run completionsinstalls Fish completions from the deployed CLI;mise run check:completionsruns outsidealland gates releases. - Skills: dot-skills owns catalog changes, links, and
check:skills; skillify owns authoring and admission. - Verify & release: dot-verify qualifies the checkout without committing;
/dot-releaseruns dot-verify, commits, pushes, and follows dot-release formise run releaseand publication checks.
Layout
dot/: Python CLI package (fmind_dot), repo-onlydot_tasks/,uv.lock, andpytestsuite.dot_agents/AGENTS.md: global persona deployed to~/.agents/AGENTS.mdfor all harnesses;dot_gemini/(agy, primary),dot_claude/,dot_copilot/, anddot_config/opencode/adapt it per host (other host state is gitignored). No custom subagent roles are deployed; see cross-harness agents.skills/&.agents/skills/: global catalog (linked into~/.agents/skills/) and repo-local skills (.claude/skillslinks to.agents/skills)..chezmoitemplates/&.chezmoiignore: JSON/TOML merge, shell block, skill-catalog, anddot-path helpers;.chezmoiignoregates repo-only, OS/Crostini-specific (including darwin-only.dockerand.zprofile), and age-key-dependent targets..github/: CI, release, security, and dependency automation;.github/assets/holds the README's SVG diagrams.- Mise trust stays machine-local (
mise trustor unmanaged~/.config/mise/conf.d/trust.toml); apply'srun_after_dot-trusthook pre-trusts configured workspaces and this checkout in the coding harnesses, not in mise.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

