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-initnpx skills add amitvijapur/cortex --skill cortex-initgit 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.00061 | $0.00885 |
| Opus 5 | $0.00030 | $0.00443 |
| Sonnet 5 | $0.00012 | $0.00177 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
cortex-init 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cortex-init — adopt the user's existing stack into Cortex
Cortex is a routing layer. This skill wires it around whatever the user already runs, instead of imposing a fixed toolset. Their systems are preserved and tied together — nothing is replaced, and their cortex.md is never overwritten without a backup and their confirmation.
Run these steps in order.
1. Discover — deterministic scan
Run the scanner:
python3 ~/.claude/bin/cortex init
It writes <state-dir>/cortex-inventory.json and prints a summary. Read the JSON. It lists their agents (counted by division), skills, commands, MCP servers, hooks, plugins, detected other-agent config files (Cursor / Codex / Gemini / Aider / Windsurf), and relevant CLIs on PATH.
2. Interview — fill gaps, don't interrogate
Auto-accept the obvious; only ask what you genuinely cannot infer. Keep it to a handful of questions. Ask about:
- Grouping: large pools (e.g. "262 agents across 21 divisions") — one "Specialist Agents" pool, or break out a few they reach for often?
- Category for any MCP/tool you can't classify from its name (search? database? scraping? design? docs?).
- Defaults per task class — for
build,review,plan,research,debug,design, which of their systems is the go-to? Offer a sensible guess and let them correct it. - Exclusions — anything detected that they do not want Cortex to route to.
Use their answers, not assumptions.
3. Synthesize the registry
Write a Workflow Registry in the exact shape Cortex uses (mirror the ## Workflow Registry section of the installed cortex.md). For each system / agent-group / skill-family / MCP:
- Installed: Yes
- Strengths: one line
- Best for: one line
- a small pattern table —
| Pattern | Use When |
Then draft a Decision Shortcuts table (task type → default route → tier) from the defaults they gave you. Ground every entry in what the scan actually found — never invent a tool they don't have.
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 · 70 lines · 61 tokens per session scan A e348b84c6975
cortex-init is a skill published in the GitHub repository amitvijapur/cortex (5 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 885 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…