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/amitvijapur/cortex/cortex-lognpx skills add amitvijapur/cortex --skill cortex-loggit clone --depth 1 https://github.com/amitvijapur/cortexWhat 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.00051 | $0.00357 |
| Opus 5 | $0.00026 | $0.00179 |
| Sonnet 5 | $0.00010 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
cortex-log 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 2d 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-log
Show the last N Cortex routing decisions from ~/.claude/cortex-log.jsonl with full reasoning.
When to invoke
- User types
/cortex-logexplicitly - User asks "what routes have I been using"
- User asks "what did cortex pick for X"
- User says "show me recent routing decisions"
- User says "audit my recent routes"
What to do
Run the cortex show command and print its output verbatim. Nothing else.
python3 ~/.claude/bin/cortex show --last 20
Optional args:
--last N— show last N routes instead of 20--project <name>— filter to a specific project
What the user sees
Each entry shows:
- Timestamp, project, task classification
- The original task description
- The chosen route (
System > Pattern > Agent @ Tier) - The reasoning tags (why this tier, why this system) — or
(obvious route)when no tags were recorded
If the log is empty, the command prints cortex log is empty — no routes logged yet.
Do NOT
- Do not aggregate or summarize the output — the user wants per-decision visibility, not stats
- Do not filter out routes unless the user explicitly asks
- Do not add commentary unless the user asks a follow-up question
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.
- 2d ago First seen · 46 lines · 51 tokens per session scan A 9104cb84e5da
cortex-log is a skill published in the GitHub repository amitvijapur/cortex (5 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 357 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.