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 skills add AdityaVG13/cortex --skill helpgit clone --depth 1 https://github.com/AdityaVG13/cortexWrote 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/skills/adityavg13/cortex/help)<a href="https://agentmods.dev/skills/adityavg13/cortex/help"><img src="https://agentmods.dev/badge/skills/adityavg13/cortex/help/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/adityavg13/cortex/help"><img src="https://agentmods.dev/badge/skills/adityavg13/cortex/help.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00028 | $0.00433 |
| Opus 5.5 | $0.00011 | $0.00173 |
| Sonnet 5.5 | $0.00006 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
help 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 28d 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
Cortex Help
Cortex remembers your decisions, conventions, and lessons across sessions. Here's how to use it:
Quick Start - Try These Now
-
Store a coding convention:
Remember: "Always use path.join() for file paths, never hardcoded / or \\" -
Recall a past bugfix:
What did I learn about race conditions in async UI code? -
Check your brain status:
/cortex:status
How to Store Knowledge
Just tell Cortex what you want it to remember:
- Conventions: "Remember: we use conventional commits (feat:, fix:, docs:)"
- Decisions: "Store: chose SQLite over Postgres for local-first storage"
- Bugfixes: "Lesson learned: NTFS file locking requires LockFileEx on Windows"
- Architecture: "Decision: API uses REST + JSON, not gRPC"
Cortex will automatically store it with context.
How to Recall Knowledge
Ask naturally:
- "What conventions do we have for error handling?"
- "Why did we choose Tokio over async-std?"
- "Remind me about the Windows path issue"
Commands
/cortex:status- Show brain status (memories, local binary, mode)/cortex:recall <query>- Search your memories (cortex_query)/cortex:store <decision>- Store a decision (cortex_commit)
Call cortex_orient once when a session starts. SessionStart injects that View automatically when the plugin is installed.
Modes
- Solo mode (default): Your brain is local at
~/.cortex/ - Live host capture:
~/.cortex/capture.jsonaftercortex setup, orCORTEX_CAPTURE
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.
- 28d ago Changed · +2 lines 86caeaac2ac6
- 1mo ago First seen · 56 lines · 28 tokens per session scan A 3c1cd293878b
help is a skill published in the GitHub repository AdityaVG13/cortex (8 stars, last pushed 28d ago), licensed MIT. It adds 28 tokens to every session and 433 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
llm-wiki
Build, ingest, query, and lint a persistent Markdown knowledge base using the Karpathy LLM Wiki pattern. Use for adding sources, maintaining interlinked wiki pages, answering from the knowledge base, filing durable research, or checking contradictions and index health. Do not use it to persist ordinary chat or…
knowledge-base
Build and maintain a company knowledge base as a wiki of interlinked markdown notes in the workspace — a private, compounding Wikipedia. Use when the user wants to start or organize a knowledge base / wiki, ingest sources (URLs, documents, pasted notes) into it, ask questions answered from it, or audit (lint) it.…
memory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
update
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
memoryguard
Local-first MCP memory backend and governance console for coding agents. Auto-organize, quarantine, supersede, and rollback shared memories across multiple agents.
memory-consolidate
Consolidate L1 memory atoms into L2 scene blocks and L3 persona. Invoked by the memory-consolidator agent, or manually via /memory-consolidate.