Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sdcorejs/sdcorejs-agentnpx agentmods add skills/sdcorejs/sdcorejs-agent/sdcorejs-exploreWrote 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-explore)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-explore"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-explore/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-explore"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-explore.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00095 | $0.05442 |
| Opus 5.5 | $0.00038 | $0.02177 |
| Sonnet 5.5 | $0.00019 | $0.01088 |
| Haiku 4.5 | $0.00010 | $0.00544 |
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 16d 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.
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 — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Path resolution: Resolve ../../_refs/... relative to this SKILL.md. Resolve another SDCoreJS skill by opening the sibling folder ../<skill-name>/SKILL.md.
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.
- 16d ago Changed · +2 lines 53810aceff15
- 25d ago Changed · -1 lines 4a6d39a68544
- 2mo ago 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,442 once invoked, about $0.0004 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…