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 skills add sdcorejs/sdcorejs-agent --skill sdcorejs-documentationgit 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-documentation)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-documentation"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-documentation/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-documentation"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-documentation.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.00104 | $0.03164 |
| Opus 5.5 | $0.00042 | $0.01266 |
| Sonnet 5.5 | $0.00021 | $0.00633 |
| Haiku 4.5 | $0.00010 | $0.00316 |
Grade A, and why
sdcorejs-documentation 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 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.
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 — 229 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.
Documentation
Shared Protocols
Read ../../_refs/shared/runtime-protocols.md; load
../../_refs/shared/documentation-layout.md only for operations below
.sdcorejs/documentation/**. Every .sdcorejs/** write applies
../../_refs/shared/artifact-lifecycle.md and emits artifact_context. Resolve
tracks through ../../_refs/shared/system-registry.json, approved artifact identity
through ../../_refs/shared/approved-artifact.mjs, and semantic repository ownership
through ../../_refs/shared/repository-contract.mjs; checkout paths and the current
working directory are never durable repository identity.
Purpose
Expose one documentation skill while keeping detailed documentation behaviors in
refs. This skill chooses the mode, loads the matching ../../_refs/documentation/*
reference, then executes it.
Long-term documentation verbs owned here:
- write
- rewrite
- improve
- structure
- summarize existing docs/artifacts
- convert
- standardize
Core Documentation Modes
Keep documentation modes distinct. Do not mix them unless the user explicitly asks for multiple outputs.
| Mode | Purpose | Primary reader | Output |
|---|---|---|---|
code-documentation |
Document source code with public contracts and/or implementation comments. | Developer using or maintaining the code. | Python docstrings, JSDoc/TSDoc, conventional doc comments, inline/block implementation comments. |
write-user-guide |
Explain how an end user, admin, or operator performs a task. | Non-developer user, admin, support, operator. | Task-oriented Markdown guide. |
write-technical-doc |
Explain system design, API behavior, integration, setup, or maintenance. | Developer, tech lead, maintainer, or API consumer. | Developer-facing Markdown documentation. |
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 3373feeef7e4
- 2mo ago First seen · 227 lines · 104 tokens per session scan A 0f10f7c4a03b
sdcorejs-documentation is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 104 tokens to every session and 3,164 once invoked, about $0.0004 per session on Opus 5.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
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…