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-explorenpx skills add sdcorejs/sdcorejs-agent --skill sdcorejs-exploregit 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.00095 | $0.05349 |
| Opus 5 | $0.00048 | $0.02674 |
| Sonnet 5 | $0.00019 | $0.01070 |
| Haiku 4.5 | $0.00010 | $0.00535 |
Grade B, and why
sdcorejs-explore scanned grade B with 1 finding 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 yesterday.
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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
| `env-setup-readonly` | Explain local setup, prerequisites, scripts, env keys, or first-run steps | Read README/config/examples and output instructions. No env/config writes. | 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.
Explore
Purpose
sdcorejs-explore is the canonical producer of project context, stack profile
evidence, and safe exploration output for downstream SDCoreJS skills.
It is read-only by default. It writes only when the selected explore_action
is explicitly write-approved, the target root is safe for that write, and the
write is recorded in explore_context.
Use it to:
- read or refresh the canonical
.sdcorejs/summary.md; - map architecture and reusable code paths;
- trace one behavior end to end;
- inspect local setup shape without changing env files;
- recover context after a break;
- read or write the target project's persona after approval;
- read or write durable memories after approval and redaction;
- read project conventions, or persist them once authorized;
- harvest documentation facts for
sdcorejs-documentation.
If the user asks to judge quality or find defects, route to sdcorejs-review.
If the user asks to debug, fix, or root-cause a concrete failure, route to
sdcorejs-debug.
If the user asks to write or run tests, route to sdcorejs-test.
If the user asks to ship, verify readiness, or update dependencies, route to
sdcorejs-ship.
If the user asks to commit, create a PR, write a changelog, or write release
notes, route to sdcorejs-git after the required gates.
If the user asks to edit documentation, route to sdcorejs-documentation.
Shared Protocols
Read _refs/shared/runtime-protocols.md. Before deep refs, broad scans,
commands, or writes, classify explore_action and load project context with:
caller_context: sdcorejs-explore;context_mode: <explore_action>;side_effects_allowed: falsefor read-only actions.
Apply _refs/shared/artifact-lifecycle.md before any write-approved action.
Use _refs/shared/system-registry.json for every track/profile classification
and _refs/shared/explore-contract.mjs for write authority and read-only
repository-topology discovery. Never reproduce their enums in prompts.
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.
- yesterday First seen · 503 lines · 95 tokens per session scan B ae3abbb884c2
sdcorejs-explore is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 95 tokens to every session and 5,349 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.