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 cdeust/Cortex --skill cortex-automategit clone --depth 1 https://github.com/cdeust/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/cdeust/cortex/cortex-automate)<a href="https://agentmods.dev/skills/cdeust/cortex/cortex-automate"><img src="https://agentmods.dev/badge/skills/cdeust/cortex/cortex-automate/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/cdeust/cortex/cortex-automate"><img src="https://agentmods.dev/badge/skills/cdeust/cortex/cortex-automate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00093 | $0.00963 |
| Opus 5.5 | $0.00037 | $0.00385 |
| Sonnet 5.5 | $0.00019 | $0.00193 |
| Haiku 4.5 | $0.00009 | $0.00096 |
Grade A, and why
cortex-automate 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 1mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automate — Triggers, Rules, and Sync
Keywords
trigger, rule, automate, remind me when, auto-remember, sync instructions, push to CLAUDE.md, prospective memory, keyword trigger, file trigger, domain trigger, time trigger, filter rule, boost rule
Overview
Set up proactive automation in Cortex — triggers that fire when conditions are met (like opening a specific file or entering a domain), rules that filter or boost memories during recall, and syncing top insights back into CLAUDE.md for persistent project instructions.
Use this skill when: You want Cortex to proactively surface information based on context, filter out noise during recall, or keep CLAUDE.md updated with memory-derived insights.
Workflow
Triggers — Proactive Memory Recall
Create triggers that fire automatically when conditions match:
Keyword trigger — fires when a query/context contains specific words:
cortex:create_trigger({
"type": "keyword",
"pattern": "authentication",
"memory_id": <id>,
"message": "Remember: we decided to use JWT with refresh tokens, not sessions"
})
File trigger — fires when a specific file is being worked on:
cortex:create_trigger({
"type": "file",
"pattern": "pg_store.py",
"memory_id": <id>,
"message": "This file has a known issue with connection pooling under load"
})
Domain trigger — fires when entering a specific project domain:
cortex:create_trigger({
"type": "domain",
"pattern": "cortex",
"memory_id": <id>,
"message": "Priority: finish the refactoring plan before adding new features"
})
Time trigger — fires after a time condition:
cortex:create_trigger({
"type": "time",
"pattern": "7d",
"memory_id": <id>,
"message": "It's been a week — run consolidation"
})
Triggers fire up to 5 times by default, then deactivate. They appear in the query_methodology response at session start.
Rules — Filter and Boost During Recall
Add rules that modify recall behavior:
Soft rule (boost/penalize score):
cortex:add_rule({
"type": "soft",
"scope": "domain:cortex",
"condition": "tag:architecture",
"weight": 1.5,
"description": "Boost architecture memories in Cortex domain"
})
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.
- 1mo ago First seen · 128 lines · 93 tokens per session scan A b843b61928dd
cortex-automate is a skill published in the GitHub repository cdeust/Cortex (75 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 963 once invoked, about $0.0004 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-30.
Other skills, from other repositories
xmemo-memory
Persistent, user-owned memory for agents. Use the standalone runtime to remember, recall, search, preserve restart continuity, manage TODOs and expenses, inspect account overview, activity and stats diagnostics, or diagnose XMemo when MCP tools are unavailable. Not for codebase search, web search, or short-lived…
knowledge-audit
Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.
temporal-query
Answer time-travel questions over stored memory — what was believed at a past point in time, when a belief changed, and what replaced it. Use when the user says "as of", "back in", "at the time", "history of", "timeline", "what did I think then", or asks why a current memory contradicts an older one.
memory-commit
Use when the user explicitly says "remember this", "save this", "ghi nho", "luu lai", "save for next time", or otherwise asks to persist the immediately preceding context. Captures with the appropriate contexttype (decision, preference, fact, skill, task, conversation) so future sessions can retrieve it accurately.
recall-context
Use at session start, before significant decisions, or when a new task references a known project to recall mnemo memories matching the current working directory, recently edited files, or topic keywords. Helps maintain continuity across sessions and avoid redoing past research.
passport-bootstrap
Use when the user installs mnemo-mcp on a fresh machine and wants to restore prior memory state from S3 or Google Drive (Phase 2 passport sync). Triggers on phrases like "set up mnemo on this machine", "restore my memory passport", "import passport", "bootstrap mnemo", or when the user says they got a new laptop / VM…