agents-local-md
Skill16 starsChanged 3 days agoISCView on GitHub
Generate machine-specific AGENTS.local.md with host facts and system tool details
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 44
If AGENTS.local.md exists in the repo root:
- Very specific: line 50
Read the file and extract the Generated: line.
- Distinctive: line 74
Only probe tools that vary across systems and affect agent behavior: zsh, tmux, nvim.
- Very specific: line 92
Write the file to the repo root (AGENTS.local.md).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
Generate AGENTS.local.md
Probe this machine's environment and write AGENTS.local.md — a machine-specific context file that Claude Code auto-loads via CLAUDE.local.md symlink.
Arguments
$ARGUMENTSOptions:
--force— regenerate even if the file is fresh
Instructions
1. Freshness Check
If AGENTS.local.md exists in the repo root:
stat -c %Y AGENTS.local.md 2>/dev/null || stat -f %m AGENTS.local.md 2>/dev/nullRead the file and extract the Generated: line. If ALL of these are true, report "AGENTS.local.md is current (generated DATE on HOSTNAME)" and stop:
- File is less than 7 days old
- Hostname in file matches current hostname
- OS in file matches current OS
--forcewas NOT passed in arguments
Otherwise, continue to regenerate.
2. Probe System Identity
Gather:
uname -s # OS kernel (Darwin/Linux)
uname -m # Architecture (x86_64/arm64)
hostname -s # Short hostname
cat /etc/os-release # Linux distro details (skip on macOS)Determine which system package manager is available:
- macOS:
command -v brew - Linux:
command -v dnforcommand -v apt
3. Probe Core System Tools
Only probe tools that vary across systems and affect agent behavior: zsh, tmux, nvim.
These are system-installed, version-significant tools where the difference between (say) zsh 5.8 vs 5.9, tmux 3.3 vs 3.5, or nvim 0.9 vs 0.11 changes what features/APIs are available. Mise-pinned tools are the same everywhere — don't list them.
For each tool, collect:
- Version:
zsh --version,tmux -V,nvim --version - Path:
command -v <tool>
4. Chezmoi Platform Detection
chezmoi data --format json | grep -E '"os"|"arch"|"hostname"'Record what chezmoi sees — this is what drives template conditionals.
5. Write AGENTS.local.md
Write the file to the repo root (AGENTS.local.md). Target <30 lines. Use this structure:
# AGENTS.local.md
> Machine-specific context for coding agents. Auto-generated — do not edit.
> Regenerate with `/agents-local-md --force`.
Generated: YYYY-MM-DD on HOSTNAME (OS ARCH)
## System
- **OS:** Fedora 42 (Linux 6.x) / macOS 15.x (Darwin)
- **Arch:** x86_64 (amd64) / arm64
- **Hostname:** name
- **Package manager:** dnf (`/usr/bin/dnf`) / brew (`/opt/homebrew/bin/brew`)
## Core Tools
| Tool | Version | Path |
|------|---------|------|
| zsh | 5.9 | `/usr/bin/zsh` |
| tmux | 3.5a | `/usr/bin/tmux` |
| nvim | 0.11.5 | `/usr/bin/nvim` |
## Chezmoi Platform
chezmoi sees: os=`linux`, arch=`amd64`, hostname=`core`What belongs here: facts that vary across machines and change agent behavior.
What does NOT belong:
- Mise-pinned tools (same everywhere)
- Third-party tools available in homebrew (latest everywhere)
- Facts already documented in the codebase (eza/dust Fedora gaps, mise wrapper alias)
- Session-ephemeral data (PID, uptime, load)
- Tool counts, shim counts, template counts
6. Create Symlink
ln -sf AGENTS.local.md CLAUDE.local.md7. Verify
test -f AGENTS.local.md && echo "AGENTS.local.md exists"
test -L CLAUDE.local.md && readlink CLAUDE.local.md
git status AGENTS.local.md CLAUDE.local.mdConfirm:
AGENTS.local.mdexists with contentCLAUDE.local.mdsymlink points toAGENTS.local.md- Both are gitignored (should not appear in
git status)
Report: "Generated AGENTS.local.md (N lines) — CLAUDE.local.md symlinked. Both gitignored."
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.

