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/aiya000/dotfiles/claude-mdgit clone --depth 1 https://github.com/aiya000/dotfilesWrote 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/instructions/aiya000/dotfiles/claude-md)<a href="https://agentmods.dev/instructions/aiya000/dotfiles/claude-md"><img src="https://agentmods.dev/badge/instructions/aiya000/dotfiles/claude-md.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.01491 | $0.01491 |
| Opus 5 | $0.00745 | $0.00745 |
| Sonnet 5 | $0.00298 | $0.00298 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade C, and why
dotfiles CLAUDE.md scanned grade C with 1 finding 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 4d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Note for me (a user): This is not a global instruction file. (This is a custom instruction file just for Claude Code and dotfiles repository.) Use '~/.dotfiles/ai-custom-instructions.md' instead if you needed. --> How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance on how Claude Code (claude.ai/code) handles the code in this repository.
Vim to Neovim Migration Guidelines
When migrating Vim configuration to Neovim:
Complete Migration Philosophy
- Migrate ALL files: Every file in the Vim configuration directory structure must be migrated faithfully to Neovim
- No function removal: Never comment out or remove functionality due to missing dependencies or different concepts between Vim and Neovim
- Implement missing concepts: When Neovim lacks a Vim concept (like autoload), implement a better custom solution rather than removing functionality
- Preserve all keymappings: All keymappings must be preserved and functional in the migrated configuration
Directory Structure Mapping
Vim (.vim/) → Neovim (.config/nvim/)
├── .vimrc → init.lua
├── autoload/**/*.vim → lua/**/*.lua (custom implementation)
├── plugin/**/*.vim → plugin/**/*.lua
├── ftdetect/**/*.vim → ftdetect/**/.lua
├── after/ftplugin/**/*.vim → after/ftplugin/**/*.lua
├── syntax/**/*.vim → syntax/**/*.lua
└── indent/**/*.vim → indent/**/*.lua
Conversion Patterns
set option=value→vim.opt.option = valuennoremap key action→vim.keymap.set('n', 'key', 'action')autocmd Event pattern action→vim.api.nvim_create_autocmd('Event', {pattern = 'pattern', callback = function() ... end})command! Name action→vim.api.nvim_create_user_command('Name', function() ... end, opts)" comment→-- comment
Vital.vim Replacement
Since vital.vim doesn't exist for Neovim, create custom Lua modules:
vital#vimrc#import('Data.List')→ require('utils.list')vital#vimrc#import('Vim.Message')→ require('utils.message')- Implement expected functionality in separate modules under
lua/utils/
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.
- 4d ago First seen · 191 lines · 1,491 tokens per session scan C 26ee529760dd
dotfiles CLAUDE.md is an instructions file published in the GitHub repository aiya000/dotfiles (19 stars, last pushed today), licensed MIT. It adds 1,491 tokens to every session, about $0.0075 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
dotfiles CLAUDE.md
Instructions for IvanWng97/dotfiles, a project described as: macOS dotfiles managed with GNU stow — ghostty, neovim, zsh, tmux, starship, lazygit, homebrew.
dotfiles CLAUDE.md
Instructions for joshukraine/dotfiles, covering claude.md, about this repository, repository structure, common commands and setup and installation.
dotfiles AGENTS.md
Instructions for helderberto/dotfiles, covering agents.md, before coding, surgical changes, verification and code principles.
dotfiles CLAUDE.md
Claude Code instructions for magic3007/dotfiles, covering claude.md, commands, ⚠️ 重要约束, architecture and two-phase installation (install.conf.yaml).
nix-config AGENTS.md
AGENTS.md instructions for dliberalesso/nix-config, covering agent instructions for nix-config, build/lint/test commands, architecture guidance, architecture and common patterns.
dotfiles AGENTS.md
AGENTS.md instructions for magic3007/dotfiles, covering agents.md, commands, architecture, two-phase installation (install.conf.yaml) and symlink model.