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 instructions/habedi/dotfiles/agents-mdgit clone --depth 1 https://github.com/habedi/dotfilesWhat 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.01391 | $0.01391 |
| Opus 5 | $0.00696 | $0.00696 |
| Sonnet 5 | $0.00278 | $0.00278 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
dotfiles AGENTS.md 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 2d ago.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to coding agents collaborating on this repository.
Mission
This is a personal dotfiles repository: shell scripts, editor and Git configuration, technical notes, AI agent skills, etc. There is no application to ship and no production runtime. Priorities, in order:
- Files that work as intended on a fresh Linux user account with bash.
- Small, self-contained, easy-to-read shell and Markdown.
- No surprise side effects: scripts must be safe to re-run.
- Technical notes and skills that stay accurate and copy-pasteable.
Core Rules
- Use English for code, comments, and docs.
- Prefer small, focused changes over large refactoring.
- Add comments only when they clarify non-obvious behavior.
- Do not add features, error handling, or abstractions beyond what the current task needs.
- Do not write a new file when editing an existing one is enough.
- Never commit secrets, tokens, or paths tied to a single machine.
Writing Style
- Use Oxford commas in inline lists: "a, b, and c" not "a, b, c".
- Do not use em dashes. Restructure the sentence, or use a colon or semicolon instead.
- Avoid colorful adjectives and adverbs. Write "TCP proxy" not "lightweight TCP proxy", "install script" not "convenient install script".
- Use noun phrases for checklist items, not imperative verbs. Write "redundant index detection" not "detect redundant indexes".
- Headings in Markdown files must be in title case: "Build from Source" not "Build from source". Minor words (a, an, the, and, but, or, for, in, on, at, to, by, of) stay lowercase unless they are the first word.
Repository Layout
scripts/: Bash scripts for system setup and maintenance (font and CLI tool installers, GPU fix, snap cleanup, file concatenation, decompression helper, system updater, and a self-destruct helper).git/gitconfig: Personal Git configuration meant to be referenced from~/.gitconfigor copied directly.docs/: Markdown sources for the technical notes, built with MkDocs Material. Currentlydocs/zig.mdanddocs/rust.md, plusdocs/index.mdas the landing page.mkdocs.yml: MkDocs configuration. Theme, navigation, and Markdown extensions live here.skills/: Markdown skill files for AI agents. Each skill lives in its own directory with aSKILL.mdentry point..editorconfig: Editor defaults (UTF-8, LF, four-space indent, final newline, trimmed trailing whitespace; Markdown, HTML, and CSS keep trailing whitespace and allow longer lines).pyproject.toml: Python environment used to host the MkDocs toolchain (mkdocs,mkdocs-material) and developer tools likepre-commit. There is no Python application code..github/workflows/docs.yml: GitHub Pages deploy job. Runsuv run mkdocs build --strictand pushes the generatedsite/to thegh-pagesbranch on push tomainordevelop, on anyv*tag, or via manual workflow dispatch..github/ISSUE_TEMPLATE/: Issue templates for bug reports and feature requests.README.md: Index of what the repository contains, with links to the deployed technical notes.
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.
- 2d ago First seen · 106 lines · 1,391 tokens per session scan A eb538b8456e4
dotfiles AGENTS.md is an instructions file published in the GitHub repository habedi/dotfiles (5 stars, last pushed 3mo ago), licensed MIT. It adds 1,391 tokens to every session, about $0.0070 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-08-31.
Other instructions, from other repositories
unity-mcp CLAUDE.md
Claude Code instructions for CoplayDev/unity-mcp, covering claude.md, what this project is, architecture, three layers on the python side and transport modes.
Unity-MCP copilot-instructions.md
Instructions for IvanMurzak/Unity-MCP, covering project guidelines, critical rules, no c# reflection for private access, code review and code style.
mcp-unity AGENTS.md
Instructions for CoderGamester/mcp-unity, covering mcp unity — ai agent guide (mcp package), purpose (what this repo is), how it works (high-level data flow), key defaults & invariants and repo layout (where to change what).
Unity-MCP CLAUDE.md
Instructions for IvanMurzak/Unity-MCP, covering claude.md, what this is, build / run, project constitution and find detail in.
unity-cli-loop AGENTS.md
AGENTS.md instructions for hatayama/unity-cli-loop, covering architecture overview, repository map, cli / unity package compatibility, project runner pin and generated skill files.
core AGENTS.md
Instructions for ReactUnity/core, covering release workflow, write changelog files, example, fix button hover state and package references.