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/sdcorejs/sdcorejs-agent/sdcorejs-plannpx skills add sdcorejs/sdcorejs-agent --skill sdcorejs-plangit clone --depth 1 https://github.com/sdcorejs/sdcorejs-agentWhat 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.00079 | $0.05362 |
| Opus 5 | $0.00039 | $0.02681 |
| Sonnet 5 | $0.00016 | $0.01072 |
| Haiku 4.5 | $0.00008 | $0.00536 |
Grade A, and why
sdcorejs-plan 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 — 503 lines — stays where its author put it; the contents beside it link to each section on GitHub.
03 - Plan
Shared Protocols
Read _refs/shared/runtime-protocols.md. Draft and approved plan artifacts apply
_refs/shared/artifact-lifecycle.md and emit artifact_context. Resolve track,
profile, and repository semantics from _refs/shared/system-registry.json; use
_refs/shared/approved-artifact.mjs for approval identity and
_refs/shared/decision-coverage.md and its .mjs authority for schema-v2 coverage and goal-backward gates.
Read _refs/sdlc/architecture.md. From _refs/shared/architecture-contract.mjs, use
validateArchitecturePrePlanHandoff before drafting, validateArchitectureDraftPlanHandoff
for draft self-review, and validateArchitecturePlanHandoff only after approval and in execution.
Purpose
Translate an approved spec into an executable contract, hold the user approval gate, and persist the approved plan corpus inside the same skill.
The plan is the exact contract that sdcorejs-execute-plan runs.
Preconditions
- A spec has explicit user approval.
sdcorejs-spechas written the approved spec snapshot.- The plan consumes
spec_context, the approved spec path/hash, and its repository ID, repository-relative path, source revision, and artifact ID. architecture_gateis an exact valid classifier result. Required work has the immutable artifact plus validatedarchitecture_context; not-applicable work uses null plus its bypass.
If the spec is missing or unapproved, route to sdcorejs-spec.
Run validateArchitecturePrePlanHandoff before drafting. Required work uses approved spec ->
approved architecture -> approved plan; a concrete bypass uses approved spec -> approved plan.
Missing parents, identity drift, mutation, unknown profiles, or owner mismatch block planning.
Before drafting, apply _refs/shared/project-context.md with:
caller_context: sdcorejs-plan
context_mode: summary-read
side_effects_allowed: true
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 · 503 lines · 79 tokens per session scan A 181fe1cade62
sdcorejs-plan is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 16d ago), licensed MIT. It adds 79 tokens to every session and 5,362 once invoked, about $0.0004 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…