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-simplifynpx skills add sdcorejs/sdcorejs-agent --skill sdcorejs-simplifygit 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.00084 | $0.01848 |
| Opus 5 | $0.00042 | $0.00924 |
| Sonnet 5 | $0.00017 | $0.00370 |
| Haiku 4.5 | $0.00008 | $0.00185 |
Grade A, and why
sdcorejs-simplify 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplify
Shared protocols
- Read
_refs/shared/runtime-protocols.md, then_refs/shared/tasklist.md; keep progress runtime-only. - Apply Project Context Preflight v2 from
_refs/shared/project-context.md. - Read repository instructions, current diffs, relevant approved artifacts, and existing project commands before deciding scope.
- Apply
_refs/shared/artifact-lifecycle.mdonly when an explicitly requested durable report is necessary. Never create a mutable session/checkpoint. - Read
_refs/shared/user-choice-prompt.mdbefore any user-facing choice or write-mode override. - Localize runtime prose. Keep identifiers, commands, paths, and reusable source English.
Purpose and ownership
Use this workflow utility for bounded refinement of current changed executable source or an explicit source scope (file, function, or path). Preserve observable behavior and prefer clarity over line count.
Do not use it as an implementation track, formatter wrapper, linter autofix, performance optimizer, bug fixer, repair loop, architecture migration, dependency cleanup, documentation or prompt rewriter, test generator, or repository-wide dead-code remover.
Keep dedicated ownership:
- read-only code or architecture assessment ->
sdcorejs-review; - structured findings ->
sdcorejs-repair-loop; - a concrete bug or failure ->
sdcorejs-debug; - tests or test-oracle changes ->
sdcorejs-test; - documentation, prompts, guides, or prose ->
sdcorejs-documentation; - broad/public/architectural refactors -> brainstorming, spec, and plan;
- approved refactor plans ->
sdcorejs-execute-plan; - dependency delivery ->
sdcorejs-ship; - Git artifacts ->
sdcorejs-git.
Load the contract
Always read:
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 · 195 lines · 84 tokens per session scan A 9f51e22ef1ac
sdcorejs-simplify is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 84 tokens to every session and 1,848 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…