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/lktiep/cortex-hub/agents-mdgit clone --depth 1 https://github.com/lktiep/cortex-hubWrote 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/lktiep/cortex-hub/agents-md)<a href="https://agentmods.dev/instructions/lktiep/cortex-hub/agents-md"><img src="https://agentmods.dev/badge/instructions/lktiep/cortex-hub/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.01093 | $0.01093 |
| Opus 5 | $0.00547 | $0.00547 |
| Sonnet 5 | $0.00219 | $0.00219 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
cortex-hub 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 4d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cortex Hub — Agent Guidelines
Current Phase: 6 (Polish, docs, testing, GA release)
Session Lifecycle
Start
cortex_session_start({ repo: "<repo URL>", mode: "development", agentId: "<your id>" })— save the returnedsessionIdcortex_knowledge_search+cortex_memory_search— recall what happened last sessioncortex_task_pickup()— check for Conductor tasks assigned to you- If
recentChanges.count > 0→git pullbefore editing
During Work
Use cortex tools as your primary workflow — they're faster, more focused, and save tokens compared to grep/find.
| What you need | Tool | Why it's better |
|---|---|---|
| Find code | cortex_code_search |
AST-aware, returns focused results (~90% fewer tokens than grep) |
| Understand a symbol | cortex_code_context |
Shows callers, callees, imports, process participation |
| Check blast radius | cortex_code_impact |
Know what breaks before you edit |
| Pre-commit risk | cortex_detect_changes |
Affected symbols + risk rating |
| Graph queries | cortex_cypher |
Direct Cypher on the knowledge graph |
| Known solutions | cortex_knowledge_search |
Search before debugging from scratch |
| Past decisions | cortex_memory_search |
Recall what you or other agents learned |
| Save a fix | cortex_knowledge_store |
Team-wide — so nobody debugs this twice |
| Save context | cortex_memory_store |
Personal recall for future sessions |
| Other agents' changes | cortex_changes |
Check before editing shared files |
| Tool effectiveness | cortex_tool_stats |
Usage analytics and success rates |
Discovery order (try in this order before falling back to grep):
memory_search → knowledge_search → code_search → code_context → code_impact → grep/find
Bug protocol: search knowledge/memory first → fix → store non-obvious fixes via knowledge_store.
End
- Verify:
pnpm build && pnpm typecheck && pnpm lint cortex_quality_report— report gate resultscortex_memory_store— persist session context (what was done, decisions, next steps)cortex_session_end(sessionId, summary)— closes session + auto-saves summary as searchable memory
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.
- 4d ago First seen · 107 lines · 1,093 tokens per session scan A 9591c811ad72
cortex-hub AGENTS.md is an instructions file published in the GitHub repository lktiep/cortex-hub (58 stars, last pushed 1mo ago), licensed MIT. It adds 1,093 tokens to every session, about $0.0055 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-30.
Other instructions, from other repositories
PrismerCloud CLAUDE.md
Instructions for Prismer-AI/PrismerCloud, covering claude.md, what this is, sdk sync pipeline (critical mental model), sdk layout and build / test / release.
Ctxo CLAUDE.md
Claude Code instructions for alperhankendi/Ctxo, covering claude.md — ctxo, project overview, quick reference, dev (pnpm workspace) and usage (consumer).
sverklo CLAUDE.md
Instructions for sverklo/sverklo, covering sverklo development, using sverklo tools, project structure and build & test.
FsLangMCP CLAUDE.md
Claude Code instructions for Neftedollar/FsLangMCP, covering fslangmcp — business workspace, how to start (required for every session), 1. determine mode, 2. load context (depends on mode) and 3. act.
Ctxo copilot-instructions.md
Copilot instructions for alperhankendi/Ctxo, covering ctxo mcp tool usage (mandatory), before any code modification, before starting a task, before reviewing a pr or diff and when exploring or searching code.
agentmako AGENTS.md
Instructions for drhalto/agentmako, covering mako mcp usage, operating model, default workflow, fast batches and freshness.