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/directivesgit clone --depth 1 https://github.com/navig-run/coreWrote 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/instructions/navig-run/core/directives)<a href="https://agentmods.dev/instructions/navig-run/core/directives"><img src="https://agentmods.dev/badge/instructions/navig-run/core/directives.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 | $0.00390 | $0.00390 |
| Opus 5 | $0.00195 | $0.00195 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
core directives.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 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.
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.
- 3d ago First seen · 39 lines · 390 tokens per session scan A f5213f7a4cba
core directives.instructions.md is an instructions file published in the GitHub repository navig-run/core (5 stars, last pushed 18d ago), with no licence file. It adds 390 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
tutor-management-app AGENTS.md
Instructions for t1112000/tutor-management-app, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
rushdb CLAUDE.md
Claude Code instructions for rush-db/rushdb, covering claude.md, git — hard rules, what this is, commands and architecture.
ndb-core entity-model.instructions.md
Instructions for Aam-Digital/ndb-core, covering entity model patterns, file naming, entity class definition, @databasefield options and custom datatypes.
knowledge-graph-system CLAUDE.md
Instructions for aaronsb/knowledge-graph-system, covering knowledge graph system - claude development guide, project overview, quick start, platform lifecycle and updates (pull images, no restart).
deployplan CLAUDE.md
Claude Code instructions for jsuncar/deployplan, a project described as: Deploy Next.js without Vercel. Supabase-like Postgres + public URL. Agent MCP: npx -y deployplan init.
YTSearch timestamp.instructions.md
Timestamp management standards and best practices for database models and service layers.