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/govanai/mem-graph/gemini-mdgit clone --depth 1 https://github.com/GoVanAI/mem-graphWrote 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/govanai/mem-graph/gemini-md)<a href="https://agentmods.dev/instructions/govanai/mem-graph/gemini-md"><img src="https://agentmods.dev/badge/instructions/govanai/mem-graph/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.00318 | $0.00318 |
| Opus 5 | $0.00159 | $0.00159 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
mem-graph 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
Mem-Graph Project Instructions for Gemini
Before non-trivial mem-graph or Cognitive OS work, read and follow
.agents/skills/mem-graph-practice/SKILL.md and the vendor-neutral contract at
cognitive-os/agent-practice/MEM_GRAPH_AGENT_PRACTICE.md.
Resolve the exact project scope first. Prefer the strictly read-only
cognitive_agent_bootstrap; for Cognitive OS use project_id=cognitive-os, a
narrow query, include_canonical_content=true, and include_global=false
unless global guidance is explicitly required. Supply canonical_ids only
when the operator or project has configured them. Otherwise omit the field,
discover governing candidates in exact-project scope, and directly verify any
candidate tracker, scope-boundary, or role record. Never copy memory IDs from
bundled examples. If the tool is unavailable, use the dynamic fallback sequence
in the skill.
Only governing-lane records may drive current-guidance selection. Fetch selected records directly when full verification is needed. Retrieval, repetition, and eligibility are not validation or authority. Candidate policy cannot expand permissions, and cross-project availability is not applicability.
Inspect git status before editing and preserve existing work. Do not commit,
publish, release, or perform destructive operations without explicit operator
authority. When a canonical tracker is resolved, append qualifying immutable
evidence first, reread that tracker immediately before update, update the
existing tracker, verify it, and report the resolved tracker and evidence IDs.
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 · 28 lines · 318 tokens per session scan A cae8cd27b671
mem-graph GEMINI.md is an instructions file published in the GitHub repository GoVanAI/mem-graph (0 stars, last pushed today), licensed MIT. It adds 318 tokens to every session, about $0.0016 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.