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/hjertefolger/cortex/cortex-configurenpx skills add hjertefolger/cortex --skill cortex-configuregit clone --depth 1 https://github.com/hjertefolger/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.00010 | $0.00784 |
| Opus 5 | $0.00005 | $0.00392 |
| Sonnet 5 | $0.00002 | $0.00157 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
cortex-configure 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cortex Configure
Adjust Cortex settings after initial setup.
Configuration Options
Presets
Offer quick presets for common configurations:
Full - All features enabled
- Statusline: enabled
- Auto-archive: enabled
- Auto-save threshold: 70%
- Awareness: enabled
Essential - Core features only
- Statusline: enabled
- Auto-archive: enabled
- Auto-save threshold: 75%
Minimal - Commands only
- Statusline: disabled
- Auto-archive: disabled
- Auto-save threshold: 85%
Individual Settings
Allow fine-tuning of specific settings:
-
Auto-save Threshold (0-100%)
- When to automatically save context
- Default: 70%
-
Restoration Token Budget (number)
- Max tokens for restoration context
- Default: 2000
-
Restoration Message Count (number)
- Number of messages to restore
- Default: 5
-
Statusline Enabled (true/false)
- Show Cortex in status line
- Default: true
-
Awareness (section)
- Injects user/time/date context at session start and after context clear
Step 1: enabled (true/false) — ask first, before anything else:
- If currently enabled: "Keep enabled", "Disable"
- If currently disabled: "Enable", "Keep disabled"
- If the user disables awareness, skip userName and timezone questions entirely.
Step 2: userName — only ask if awareness is enabled:
- If already set (show current value): "Keep current", "Change" (ask for new name), "Turn off" (set null)
- If not set: "Set a name" (ask for name string), "Skip" (keep null)
- IMPORTANT: Never pre-fill or guess the user's name. Always let the user type it.
Step 3: timezone — only ask if awareness is enabled:
- "Auto-detect" → set null (uses system timezone)
- "Custom" → ask user for IANA timezone string (e.g. "America/New_York")
- "Off" → set "off" (omit Date/Time lines entirely, only show User if set)
- IMPORTANT: Never pre-fill a timezone value. Let the user choose and type.
Usage Flow
- Ask user what they want to configure:
- Apply a preset
- Adjust specific settings
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 · 117 lines · 10 tokens per session scan A 2581a862711c
cortex-configure is a skill published in the GitHub repository hjertefolger/cortex (174 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 784 once invoked, about $0.0001 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
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.