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/johnnichev/nv-context/gemini-mdgit clone --depth 1 https://github.com/johnnichev/nv-contextWrote 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/johnnichev/nv-context/gemini-md)<a href="https://agentmods.dev/instructions/johnnichev/nv-context/gemini-md"><img src="https://agentmods.dev/badge/instructions/johnnichev/nv-context/gemini-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 | $0.00082 | $0.00082 |
| Opus 5 | $0.00041 | $0.00041 |
| Sonnet 5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
nv-context GEMINI.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
nv:context — Gemini CLI Support
Skill
nv-context— Context engineering setup for any repository.
Tool Mapping
Read→read_fileWrite→write_fileEdit→edit_fileGlob→globGrep→grepBash→shell
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 · 15 lines · 82 tokens per session scan A a3a1256c2d64
nv-context GEMINI.md is an instructions file published in the GitHub repository johnnichev/nv-context (7 stars, last pushed 4mo ago), licensed MIT. It adds 82 tokens to every session, about $0.0004 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
harness-engineering CLAUDE.md
Instructions for jrenaldi79/harness-engineering, covering claude.md, project overview, core features, essential commands and testing.
vibe-27 AGENTS.md
AGENTS.md instructions for fatalex27/vibe-27, covering vibe-27 behavioral guidelines, 1. editor, not typist, 2. intention over implementation, 3. trust and verify and 4. think before coding.
lynxprompt-vscode CLAUDE.md
Claude Code instructions for GeiserX/lynxprompt-vscode, covering claude.md — lynxprompt vs code, tech stack, development, architecture and key commands.
sourcebook CLAUDE.md
Claude Code instructions for maroondlabs/sourcebook, covering claude.md, commands, critical constraints, architecture and deprecated patterns.
vibe-27 CLAUDE.md
Claude Code instructions for fatalex27/vibe-27, covering vibe-27 behavioral guidelines, 1. editor, not typist, 2. intention over implementation, 3. trust and verify and 4. think before coding.
agent-ready-repo AGENTS.md
AGENTS.md instructions for eugenelim/agent-ready-repo, covering agents.md, project overview, rule lookups, documentation and development workflow.