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 skills/julymetodiev/post-cortex/agentsnpx skills add julymetodiev/post-cortex --skill agentsgit clone --depth 1 https://github.com/julymetodiev/post-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/julymetodiev/post-cortex/agents)<a href="https://agentmods.dev/skills/julymetodiev/post-cortex/agents"><img src="https://agentmods.dev/badge/skills/julymetodiev/post-cortex/agents.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.00039 | $0.00597 |
| Opus 5 | $0.00019 | $0.00298 |
| Sonnet 5 | $0.00008 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
post-cortex-agents 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Cortex Agent System
Specialized agents for Post-Cortex memory operations using 6 consolidated MCP tools.
Agents
| Agent | subagent_type | Purpose | Model |
|---|---|---|---|
| Context Builder | context-builder |
Log decisions, Q&A, problems, code changes | Haiku |
| Search Specialist | search-specialist |
Find past knowledge, semantic search | Sonnet |
| Knowledge Analyst | knowledge-analyst |
Summaries, analysis, entity mapping | Opus |
| Memory Curator | memory-curator |
Session/workspace management | Haiku |
MCP Tools (6 Consolidated)
| Tool | Purpose |
|---|---|
session |
Create/list sessions |
update_conversation_context |
Add context (single or bulk) |
semantic_search |
Universal search with scope |
get_structured_summary |
Session summaries |
query_conversation_context |
Entity analysis, keyword search |
manage_workspace |
Workspace CRUD operations |
Agent Routing
| User Intent | Route To |
|---|---|
| "find", "search", "what did we discuss" | search-specialist |
| "remember", "log", "decided", "fixed" | context-builder |
| "summarize", "analyze", "insights" | knowledge-analyst |
| "create session", "new workspace" | memory-curator |
Session Protocol
Every operation requires a session_id. Get it from:
- CLAUDE.md (project configuration)
session(action: "list")to find existingsession(action: "create")for new sessions
Multi-Step Workflows
Knowledge Retrieval (session → workspace → global)
1. semantic_search(query, scope="session", scope_id=session_id)
2. IF no results: semantic_search(query, scope="workspace", scope_id=workspace_id)
3. IF no results: semantic_search(query, scope="global")
4. Synthesize and respond
Context Capture
1. Identify type: qa | decision_made | problem_solved | code_change | requirement_added | concept_defined
2. Structure content as key-value pairs
3. update_conversation_context(session_id, interaction_type, content)
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 69 lines · 39 tokens per session scan A aadd1e56b8b5
post-cortex-agents is a skill published in the GitHub repository julymetodiev/post-cortex (20 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 597 once invoked, about $0.0002 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 skills, from other repositories
memora
Use when working with persistent memory across sessions, storing/retrieving knowledge, managing TODOs/issues, or when context from previous sessions would be helpful.
lemmalog
Externalize working memory and logical state into the lemmalog Datalog engine (MCP). Use for ANY multi-step task where state should outlive one context window or span agents: long investigations, debugging sessions, audits, multi-agent searches, systematic explorations, planning with many interdependent constraints…
dbrain-processor
Personal assistant for processing daily voice/text entries from Telegram. Classifies content, saves thoughts to Obsidian with wiki-links, generates HTML reports. Integrates Your Business context (clients, projects, CRM). Triggers on /process command or daily 21:00 cron.
autograph
Schema-as-code enforcement for any Obsidian vault. Zero hardcoded domains. Use when creating vault cards, checking vault health, running schema compliance, deduplicating entities, generating MOC indexes, running decay cycles, bootstrapping a vault, fixing wikilinks, finding orphans or backlinks, extracting entities…
ori-memory
Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.
braindb
Memory recall and save. Use at every conversation start and whenever the user shares personal information, expertise, project context, preferences, or decisions worth remembering long-term.