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/navig-run/core/devgit clone --depth 1 https://github.com/navig-run/coreWhat 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.00386 | $0.00386 |
| Opus 5 | $0.00193 | $0.00193 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
core dev.instructions.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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 40 lines · 386 tokens per session scan A 2ede2c10c86e
core dev.instructions.md is an instructions file published in the GitHub repository navig-run/core (5 stars, last pushed 16d ago), with no licence file. It adds 386 tokens to every session, about $0.0019 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
appwrite AGENTS.md
Instructions for appwrite/appwrite, covering appwrite, commands, stack, layout and libraries.
netdata AGENTS.md
AGENTS.md instructions for netdata/netdata, covering agents.md, goals, requirement language, mandatory development principles and sow system.
meme-search CLAUDE.md
Instructions for neonwatty/meme-search, covering claude.md, 📁 file organization guidelines, 🤖 task agent usage guidelines, when to use task agents and documentation lookup pattern.
selfhost-ai CLAUDE.md
Instructions for kossakovsky/selfhost-ai, covering claude.md, project overview, core architecture, key files and installation flow.
SForum AGENTS.md
Instructions for zhuchunshu/SForum, covering agent guide, project intent, working principles, stack and directory map and commands.
redd-archiver CLAUDE.md
Instructions for 19-84/redd-archiver, covering claude.md, project overview, deviations from global standards, build & run commands and docker development (primary method).