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 skills add aiya000/dotfiles --skill read-agents-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/skills/aiya000/dotfiles/read-agents-md)<a href="https://agentmods.dev/skills/aiya000/dotfiles/read-agents-md"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/read-agents-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.1 | $0.00064 | $0.00472 |
| Opus 5 | $0.00032 | $0.00236 |
| Sonnet 5 | $0.00013 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
read-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 7d 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.
What it actually says
read-agents-md
Reading AGENTS.md
Read the following files in order (skip any that do not exist):
~/.dotfiles/AGENTS.global.md— global agent instructions shared across all projects- All
AGENTS.mdfiles along the path from the current directory up to the project root (inclusive on both ends)
To find the files for step 2:
- Determine the project root with
git rev-parse --show-toplevel(or treat the current directory as root if not in a git repo) - Walk from the current directory up to the project root, collecting each directory that contains an
AGENTS.md - Read them from outermost (project root) to innermost (current directory)
After reading all found files, say 'AGENTS.md loaded!'
On first access to a file in a directory
The first time you access (read or write) any file in a directory whose files you have not touched yet in this session, read that directory's AGENTS.md if it exists and has not been loaded yet.
Rules:
- "First access" means the first time in the session you read or write any file inside that directory
- Only the
AGENTS.mddirectly in that immediate directory is loaded — do not search parent directories here - If the directory has no
AGENTS.md, nothing is loaded - Each directory's
AGENTS.mdis loaded at most once per session - When you load a new directory's
AGENTS.mdthis way, also re-read everyAGENTS.mdyou have already loaded in this session (including the current directory's), so all of them stay fresh in context
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.
- 7d ago First seen · 35 lines · 64 tokens per session scan A 94833305d1c4
read-agents-md is a skill published in the GitHub repository aiya000/dotfiles (19 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 472 once invoked, about $0.0003 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 skills, from other repositories
restart__pull_request
A pull-request restart workflow for replacing a messy review with a new pull request containing one clean commit and a summary of the earlier discussion.
rescue__pull_request_review
An automated workflow for handling GitHub pull-request review comments, applying requested code changes, committing them, and pushing them back.
submit__pull_request
An automated pull-request submission workflow. A pull request is a request for a code change to be reviewed and merged; this workflow writes its explanation, creates it, watches its automated checks, and fixes failed checks.
write__pull_request
A workflow for writing a pull request description, the explanation attached to a proposed code change for review. It analyses the changes and commit history.
monitor__ci_status
An automated monitor for GitHub Actions, the service that runs checks such as tests after code changes. It watches all checks after a pull request or a push to a pull-request branch and can invoke a failure-recovery process.
monitor__pull_request_conflict
An automated check for GitHub pull requests, which are proposed code changes awaiting review or merging.