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/magic3007/dotfiles/agents-mdgit clone --depth 1 https://github.com/magic3007/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.02522 | $0.02522 |
| Opus 5 | $0.01261 | $0.01261 |
| Sonnet 5 | $0.00504 | $0.00504 |
| Haiku 4.5 | $0.00252 | $0.00252 |
Grade C, and why
dotfiles AGENTS.md scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
**omp** (`omp/`, https://omp.sh, Stencil/oh-my-pi): a coding agent harness. Only `~/.omp/agent/config.yml -> omp/config.yml` is symlinked; the rest of `~/.omp/agent` (`*.db`, `sessions/`, `cache/`, ...) is runtime state Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**omp** (`omp/`, https://omp.sh, Stencil/oh-my-pi): a coding agent harness. Only `~/.omp/agent/config.yml -> omp/config.yml` is symlinked; the rest of `~/.omp/agent` (`*.db`, `sessions/`, `cache/`, ...) is runtime state How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex (Codex.ai/code) when working with code in this repository.
Overview
Dotfiles repository using Dotbot for installation. Stores configuration files and symlinks them to their standard locations (~/.zshrc, ~/.gitconfig, ~/.config/nvim, etc.).
Commands
./install # Full installation (idempotent, safe to re-run)
./install -n # Dry run — preview what would be installed
git submodule update --init --recursive # Update Vim plugins
Architecture
Two-Phase Installation (install.conf.yaml)
- Phase 1 — Local: Defaults, directory creation, submodules, backup existing configs, symlinks. No network required, always succeeds.
- Phase 2 — Network: Homebrew, platform packages, oh-my-zsh + plugins, fzf, Node.js/nvm, GitHub CLI, AI coding tools. All commands use
--connect-timeout/|| trueto avoid blocking without network.
Symlink Model
All configs live in this repo and are symlinked to ~ via Dotbot. The link section in install.conf.yaml is the single source of truth for what gets symlinked where. When adding new configs: add files to the repo, then add symlink entries to install.conf.yaml.
Local Customization Pattern
Machine-specific overrides go in *_local files (not tracked by git):
~/.gitconfig_local— local git user/config (included via[include]in gitconfig)~/.zsh_local— local zsh config~/.common_shell_setup_local.sh— local shell setup (bash/zsh)~/.config/fish/conf.d/local.fish— local fish config
Shell Setup
Three shells are supported: zsh, bash, and fish.
bash/zsh: common_shell_setup.sh is sourced by both .zshrc and .bashrc. It contains shared aliases, functions, env vars, and AI tool wrappers.
fish: fish/ directory is symlinked to ~/.config/fish/. Fish config is maintained separately (not sourced from common_shell_setup.sh) because fish syntax is incompatible with POSIX shell. Structure:
config.fish— tool initialization (starship, zoxide, conda, venv)conf.d/— modular config (env vars, PATH, aliases, fzf, ssh)functions/— lazy-loaded functions (one per file, fish best practice)fish_plugins— Fisher plugin list- AI tool wrappers use
_claude_with_apihelper function to reduce duplication
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 · 143 lines · 2,522 tokens per session scan C 8610ba4a5de1
dotfiles AGENTS.md is an instructions file published in the GitHub repository magic3007/dotfiles (10 stars, last pushed 6d ago), licensed MIT. It adds 2,522 tokens to every session, about $0.0126 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
dotfiles AGENTS.md
Cross-platform dotfiles managed by Chezmoi with Homebrew/apt and per-language version managers. One-command bootstrap for macOS and Linux with Neovim, Tmux, Zsh, and AI agent skills.
dotfiles CLAUDE.md
Claude Code instructions for ooloth/dotfiles, covering claude.md, uphold project invariants, folder structure, symlink management and claude development workflow.
dotfiles CLAUDE.md
Instructions for nicknisi/dotfiles, covering dotfiles, structure, setup and key conventions.
dotfiles CLAUDE.md
Instructions for IvanWng97/dotfiles, a project described as: macOS dotfiles managed with GNU stow — ghostty, neovim, zsh, tmux, starship, lazygit, homebrew.
j3w1zsh AGENTS.md
AGENTS.md instructions for j3w1/j3w1zsh, covering j3w1zsh agent instructions, purpose and authority, start every run, security and privacy and platform and installer contract.
dotfiles copilot-instructions.md
Copilot instructions for edbizarro/dotfiles, covering agents, what this is, critical: non-obvious patterns, zsh has a special stow structure and multi-distro conditional logic.