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/jackfranklin/dotfiles/claude-mdgit clone --depth 1 https://github.com/jackfranklin/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.00976 | $0.00976 |
| Opus 5 | $0.00488 | $0.00488 |
| Sonnet 5 | $0.00195 | $0.00195 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
dotfiles CLAUDE.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 3d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Overview
Personal dotfiles for Jack Franklin. Uses a symlink-based installation strategy: files are stored in this repo without a leading dot, then symlinked into place with make <target>. No stow — the Makefile manages all symlinks explicitly.
Common Commands
# Run Lua unit tests (requires busted)
make lua_specs
# Install individual tool configs (creates symlinks)
make neovim # ~/dotfiles/nvim → ~/.config/nvim
make fish # ~/dotfiles/fish → ~/.config/fish
make git # gitconfig + gitignore_global → ~/.gitconfig / ~/.gitignore_global
make kitty # ~/dotfiles/kitty → ~/.config/kitty
make claude # settings.json + CLAUDE.md + skills → ~/.claude/
# Install system packages (Ubuntu/Debian)
make ubuntu-deps
# Install global npm language servers (TypeScript, Svelte, ESLint, etc.)
make language_servers_global
Architecture
Installation Model
Each make target runs ln -nsf to create a symlink. There is no automatic install — targets must be run individually. The DIR variable defaults to ~/dotfiles.
Neovim (nvim/)
All Neovim config is Lua under nvim/lua/jack/. Entry point is nvim/init.lua.
Plugin system: Plugins are declared in nvim/lua/jack/load_plugins.lua as a single base_plugins() table. M.load(config) supports three override keys:
extra_plugins— add plugins not in baseconfig_overrides— replace a plugin'sconfigfunction by plugin name/dirdelete_plugins— exclude a plugin from loading
This allows per_machine.lua to customise plugins without modifying the shared list.
Plugin configs live in nvim/lua/jack/plugins/<plugin-name>.lua and are require()d from the plugin's config function.
LSP setup (nvim/lua/jack/lsp-config.lua) exports per-server setup functions (M.typescript, M.deno, M.eslint, M.lua, M.css). These must be called explicitly — typically from nvim/lua/jack/plugins/lsp.lua or per_machine.lua.
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.
- 3d ago First seen · 75 lines · 976 tokens per session scan A 2b2473b3bcbc
dotfiles CLAUDE.md is an instructions file published in the GitHub repository jackfranklin/dotfiles (254 stars, last pushed 10d ago), licensed MIT. It adds 976 tokens to every session, about $0.0049 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.