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/ychamel/reporesident/agents-mdgit clone --depth 1 https://github.com/ychamel/RepoResidentWhat 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.00050 | $0.00050 |
| Opus 5 | $0.00025 | $0.00025 |
| Sonnet 5 | $0.00010 | $0.00010 |
| Haiku 4.5 | $0.00005 | $0.00005 |
Grade A, and why
RepoResident 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 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.
What it actually says
Agent entry point: read CLAUDE.md in full — it is the operating manual — then follow its
Session protocol. Everything else (state, workflows, project knowledge) is routed from there
via the .agent/ directory.
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 · 4 lines · 50 tokens per session scan A 8a4fc5b11add
RepoResident AGENTS.md is an instructions file published in the GitHub repository ychamel/RepoResident (6 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session, 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-31.
Other instructions, from other repositories
dmux AGENTS.md
Instructions for standardagents/dmux, covering agents.md - dmux maintainer guide, docs map, project overview, important architecture landmarks and native helper.
thinkrail AGENTS.md
Instructions for JetBrains/thinkrail, covering thinkrail, module structure & boundaries (top-priority requirement), engine: pi only, in-process, architecture (three rings) and repo layout.
metis AGENTS.md
Instructions for Wholiver/metis, covering agent development guide, objective, start every task, repository map and desktop frontend changes (mandatory).
cctop AGENTS.md
Instructions for st0012/cctop, covering agents.md - development guide for cctop, scope and sources, required development rules, driver workflow and github and pr rules.
pixir CLAUDE.md
Instructions for Ranvier-Technologies/pixir, covering pixir harness - legacy agent guide, current map and commands.
slipway AGENTS.md
Instructions for signalridge/slipway, covering slipway agent principles, user owns the process, investigate before clarifying, report, do not certify and maintain the whole surface.