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/imayuur/contexthub/agents-mdgit clone --depth 1 https://github.com/iMayuuR/contexthubWrote 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/imayuur/contexthub/agents-md)<a href="https://agentmods.dev/instructions/imayuur/contexthub/agents-md"><img src="https://agentmods.dev/badge/instructions/imayuur/contexthub/agents-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.00615 | $0.00615 |
| Opus 5 | $0.00308 | $0.00308 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
contexthub AGENTS.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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ContextHub (all agents)
ContextHub — Secure Auto-Memory Policy
ContextHub stores encrypted project memory locally (AES-256-GCM). Agents must use MCP tools — no shell logging or shell profile changes.
Required workflow (every session)
- Session start —
ensure_sessionwith agent name:cursor,claude-code,windsurf,copilot,codex, or your client id. - Before answering —
get_project_context; usesearch_memory/semantic_searchwhen prior context may help. - After each meaningful turn —
record_turnwith concise prompt + response summaries (decisions, bugs, architecture). - Session end —
end_sessionwith the active session id.
When to call record_turn automatically (do not ask the user)
- Architectural or design decisions
- Bug root cause and fix
- Non-obvious repo conventions
- Security-relevant behavior
- Breaking changes
Skip: small talk, pure formatting, duplicate facts already stored.
Security (mandatory)
- Never read or output
.contexthub/.keyfile - Never store API keys, passwords, tokens, or private keys
- Never scan
.env,.pem,.key,id_rsafor memory content - Use repo-relative paths only
Tool cheat sheet
| Goal | Tool |
|---|---|
| Start session | ensure_session |
| Save a turn | record_turn |
| Single note | save_memory |
| Unified query | contexthub_query |
| Find context | search_memory, semantic_search |
| Context bundle | get_context_bundle |
| Code graph stats | get_code_graph_stats |
| Related symbols | get_related_symbols |
| Blast radius | get_blast_radius |
| Trace path | trace_code_path |
| Search by code | search_memory_by_code |
| Full policy text | get_agent_policy |
🧠 DeepSync — Instant Repo Intelligence
Run npx @imayuur/contexthub deepsync once to build a complete knowledge graph of your codebase — code, docs, and git history. After that, context auto-updates every session via ensure_session. No manual effort needed.
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 · 67 lines · 615 tokens per session scan A fec73b8e2d63
contexthub AGENTS.md is an instructions file published in the GitHub repository iMayuuR/contexthub (0 stars, last pushed 3mo ago), licensed MIT. It adds 615 tokens to every session, about $0.0031 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
vespertide AGENTS.md
AGENTS.md instructions for dev-five-git/vespertide, covering vespertide knowledge base, structure, where to look, data flow and conventions.
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
RNR-Enhanced-Cognee AGENTS.md
AGENTS.md instructions for vincentspereira/RNR-Enhanced-Cognee, covering rnr enhanced cognee implementation for codex, critical requirements, 1. ascii-only output (no unicode encoding), 2. dynamic categories (no hardcoded categories) and 3. standard memory mcp interface.
memory-mcp-1file AGENTS.md
Instructions for pomazanbohdan/memory-mcp-1file, covering ⛔ l0 invariants (never violate under any circumstance), detection heuristic, 🔀 phase transition routing (⛔ blocking), gate-0: phase identification & loading and 🧾 proof-of-load requirement (critical).