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/claude-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/claude-md)<a href="https://agentmods.dev/instructions/govanai/mem-graph/claude-md"><img src="https://agentmods.dev/badge/instructions/govanai/mem-graph/claude-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.00921 | $0.00921 |
| Opus 5 | $0.00461 | $0.00461 |
| Sonnet 5 | $0.00184 | $0.00184 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
mem-graph CLAUDE.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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mem-Graph Project Instructions for Claude
This file adds repository-specific routing to the global Claude rules. It is a startup contract, not the source of live milestone state.
Before non-trivial mem-graph or Cognitive OS work, read and follow
.agents/skills/mem-graph-practice/SKILL.md. Its vendor-neutral source is
cognitive-os/agent-practice/practice.v1.json; generated host adapters must not
be edited by hand.
Scope
Cognitive OS is a global, cross-project agent framework. This repository is its current additive proving ground and persistence substrate; it is not the framework's architectural boundary. Canonical tracker, scope-boundary, and optional role-record IDs are deployment-local and must come from operator or project configuration, not from this repository.
Use project_id=cognitive-os for Cognitive OS governance, experiments,
policies, event evidence, roadmap work, and program state. Keep unrelated
mem-graph substrate work in its applicable project scope. Cross-project
availability never implies automatic applicability.
Mandatory Cognitive OS Bootstrap
Before reviewing, changing, or recording Cognitive OS work:
- Prefer
cognitive_agent_bootstrapwithproject_id=cognitive-os, a narrow task query,include_canonical_content=true, andinclude_global=falseunless global guidance is explicitly required. Supplycanonical_idsonly when the operator or project has configured tracker, scope-boundary, or role records; otherwise omit it and discover governing candidates. The bootstrap does not touch access tracking or write a receipt. - Directly verify any candidate canonical records. When a tracker is resolved, read the roadmap and active artifacts it references before modifying implementation or judging milestone completion.
- Fetch selected records directly when their full content or authority still needs verification. A verified, operator/project-designated tracker—not a static onboarding example—is the authority for current program state.
- If the bootstrap tool is unavailable, use the dynamic fallback sequence:
resolve configured canonical IDs or discover exact-project governing
candidates;
memory_geteach resolved record; read referenced roadmap/artifacts;cognitive_policy_lookupforrequest_type/current_canonical_guidance; exact-project guidance search or diagnosis; and direct fetch of every selected record.
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 · 97 lines · 921 tokens per session scan A ba42165c7e7d
mem-graph CLAUDE.md is an instructions file published in the GitHub repository GoVanAI/mem-graph (0 stars, last pushed today), licensed MIT. It adds 921 tokens to every session, about $0.0046 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.