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-using-skillsnpx skills add sdcorejs/sdcorejs-agent --skill sdcorejs-using-skillsgit clone --depth 1 https://github.com/sdcorejs/sdcorejs-agentWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-using-skills)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-using-skills"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-using-skills.svg" alt="Measured on agentmods" height="20"></a>What 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.00072 | $0.01678 |
| Opus 5 | $0.00036 | $0.00839 |
| Sonnet 5 | $0.00014 | $0.00336 |
| Haiku 4.5 | $0.00007 | $0.00168 |
Grade A, and why
sdcorejs-using-skills 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 4d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using sdcorejs Skills
Bootstrap
Match skill descriptions before reading bodies. Load
_refs/shared/runtime-protocols.md, then only the references required by the
selected task. Current user instructions and current evidence override stored
context. _refs/shared/system-registry.json is the versioned source of truth
for track, stack-profile, artifact-kind, repository-role, review, repair, ship,
and evidence semantics. Read only the registry fields needed for the selected
route; do not load every referenced track body during bootstrap.
Priority when several skills match:
- Explicit skill named by the user.
- Approved plan continuation:
sdcorejs-execute-plan. - Product, design, and direct test work:
sdcorejs-product,sdcorejs-design,sdcorejs-test; failing-test diagnosis usessdcorejs-debug. - Dedicated intent:
sdcorejs-simplify,sdcorejs-explore,sdcorejs-documentation,sdcorejs-review,sdcorejs-repair-loop,sdcorejs-debug,sdcorejs-ship, orsdcorejs-git. - Confirmed implementation:
sdcorejs-ai-agent,sdcorejs-angular,sdcorejs-nestjs, orsdcorejs-nextjs. - Open-ended, ambiguous, or under-specified change:
sdcorejs-brainstorming.
Entry Gate
Choose one path before loading a full workflow:
- Pure Q&A with no authorized write: answer directly.
- Small, explicit, low-risk fix: targeted context, smallest scoped edit, focused verification, and concise review. Behavior, acceptance criteria, ownership, and verification must already be bounded.
- Ambiguous, architectural, cross-cutting, security-sensitive, destructive, concurrency-sensitive, or public-contract change: full workflow.
Imperative verbs such as implement, build, or create express write intent
only; they are not spec approval or plan approval. Apply the selected path's
entry criteria and approval artifacts independently of the wording of the
requested outcome. A fixture, lab, benchmark, or disposable repository does not
waive a required approval gate, and an explicit scoped prompt is not a substitute
for a required artifact.
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.
- 4d ago First seen · 150 lines · 72 tokens per session scan A 11e875886782
sdcorejs-using-skills is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 17d ago), licensed MIT. It adds 72 tokens to every session and 1,678 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…