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-designnpx skills add sdcorejs/sdcorejs-agent --skill sdcorejs-designgit 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.00085 | $0.05084 |
| Opus 5 | $0.00043 | $0.02542 |
| Sonnet 5 | $0.00017 | $0.01017 |
| Haiku 4.5 | $0.00009 | $0.00508 |
Grade A, and why
sdcorejs-design 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 — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Track
Shared Protocols
Read _refs/shared/runtime-protocols.md and
_refs/shared/artifact-lifecycle.md; load
_refs/shared/design-handoff.md for durable handoffs. Consume canonical
track/profile and artifact values from _refs/shared/system-registry.json,
canonical artifact roots from _refs/shared/artifact-paths.mjs, verify approved
spec/plan parents with _refs/shared/approved-artifact.mjs, and resolve semantic
ownership with _refs/shared/repository-contract.mjs. Emit artifact_context
for every design artifact and ledger written. Never rebuild a Design path by
hand.
Purpose
Create FE handoff artifacts from product intent. The output should let Angular/Next.js executors implement screens without guessing layout, states, copy, interactions, or responsive behavior.
Design does not write production code, replace a spec/plan, mutate an approved artifact, invent behavior outside approved requirements, or create module code.
PNG generation is feasible, but a PNG alone is not a reliable source of truth. For exact FE implementation, always pair PNG previews with editable design artifacts and a written handoff spec.
Before designing UI from PRDs, user stories, acceptance criteria, or rough
feature briefs, read _refs/design/frontend-design.md. Use it to create a
compact visual direction, token plan, signature element, copy voice, and
self-critique before writing final design specs or wireframes.
For frontend handoff, also read _refs/shared/frontend-architecture.md. Use
repository evidence to produce an implementation-oriented component/data/
interaction map. Design may propose candidate boundaries, but it must not claim
exact code paths, providers, or public exports are confirmed when the target
codebase has not been inspected.
When the target surface is a mobile app, PWA, responsive mobile web experience,
or explicitly mobile-first screen/flow, also read
_refs/design/mobile-design.md. Use it to add mobile context, platform fit,
touch ergonomics, navigation, mobile state coverage, and implementation
governance to the handoff.
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 · 490 lines · 85 tokens per session scan A f317e3e021b5
sdcorejs-design is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 16d ago), licensed MIT. It adds 85 tokens to every session and 5,084 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…