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/valsecchi75/project-scaffolder/cortexnpx skills add valsecchi75/project-scaffolder --skill cortexgit clone --depth 1 https://github.com/valsecchi75/project-scaffolderWhat 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.00065 | $0.03234 |
| Opus 5 | $0.00032 | $0.01617 |
| Sonnet 5 | $0.00013 | $0.00647 |
| Haiku 4.5 | $0.00006 | $0.00323 |
Grade A, and why
cortex 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 3d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cortex — The Project Leader
Overview
Cortex is the orchestration layer that turns a task into a verified, tested, and learned-from delivery. It classifies work, finds or generates the right skills, delegates to specialist subagents, runs quality gates, and feeds results back to the skill network via Synapse.
Core principle: Every task goes through classify → execute → verify → learn. No shortcuts except for explicitly trivial work.
Activation
Explicit activation
The /task command always triggers the full Cortex pipeline.
Implicit activation
When a user describes work during a development session (post-scaffolding), Cortex evaluates:
Activate when the message contains an imperative verb targeting a code artifact:
- "implement", "add", "fix", "create", "refactor", "build", "remove", "update", "migrate"
Do NOT activate for:
- Questions: "how does X work?", "what is Y?", "explain Z"
- Wiki/doc requests: "update the handoff", "document this decision"
- Simple file reads or exploration
When uncertain: Ask "Should I run this through the full task pipeline, or handle it directly?"
v2.0 default: Implicit activation always asks for confirmation. Only /task activates without confirmation.
The Pipeline
Step 0: Execution Doc gate (v3)
Before any classification:
- Determine the current phase N from CLAUDE.md ("Current phase").
- Check that
docs/phases/PHASE-{N}-execution.mdexists.- Missing → STOP the pipeline. Reply exactly: "Fase {N} senza Execution Doc — esegui
/phase-docprima di assegnare task." Log the refusal tologs/pipeline/. - Exception: the
--no-phase-docflag skips the gate. Log it as a conscious choice:[GATE-SKIPPED by user flag].
- Missing → STOP the pipeline. Reply exactly: "Fase {N} senza Execution Doc — esegui
- If the doc exists: read the Activities table, match the task against an activity, and use its assigned Model as the routing hint for the specialist subagent (Step 4). If the task matches no activity, ask the user whether to add it to the doc or proceed as unplanned work (logged).
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.
- 3d ago First seen · 285 lines · 65 tokens per session scan A 4de926c28be8
cortex is a skill published in the GitHub repository valsecchi75/project-scaffolder (9 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 3,234 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…