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 notify-instruction-file-loadedgit 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/notify-instruction-file-loaded)<a href="https://agentmods.dev/skills/aiya000/dotfiles/notify-instruction-file-loaded"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/notify-instruction-file-loaded/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aiya000/dotfiles/notify-instruction-file-loaded"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/notify-instruction-file-loaded.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.00325 |
| Opus 5 | $0.00022 | $0.00162 |
| Sonnet 5 | $0.00009 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
notify-instruction-file-loaded 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 9d 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
notify-instruction-file-loaded
Say the appropriate loaded message based on the path of the instructions file that was just read.
Behavior
Determine the message based on the file path:
| Condition | Message |
|---|---|
Path is ~/.claude/CLAUDE.md or resolves to it |
Global CLAUDE.md loaded! |
Path is {project-root}/.claude/CLAUDE.md or any other CLAUDE.md |
Local CLAUDE.md loaded! |
Path is ~/AGENTS.md or ~/AGENTS.global.md |
Global AGENTS.md loaded! |
| Path is any other AGENTS.md (project subdirectory, etc.) | Local AGENTS.md loaded! |
Classification Rules
- Global vs Local: If the file lives under the user's home directory config (
~/.claude/) or is the home-directory-level AGENTS.md / AGENTS.global.md → Global. Otherwise → Local. - CLAUDE vs AGENTS: Determined by the file name (
CLAUDE.md→ CLAUDE,AGENTS.mdorAGENTS.global.md→ AGENTS).
Does Not
- Read or modify any files
- Do anything other than say the single loaded message
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.
- 9d ago First seen · 30 lines · 43 tokens per session scan A 7fa0c028517a
notify-instruction-file-loaded is a skill published in the GitHub repository aiya000/dotfiles (19 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 325 once invoked, about $0.0002 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.
rescue__pull_request_conflict
An automated procedure for resolving merge conflicts in a pull request branch. A merge conflict happens when Git cannot combine competing changes by itself.