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-ai-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-ai-agent)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-ai-agent"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-ai-agent/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-ai-agent"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-ai-agent.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.00081 | $0.02263 |
| Opus 5.5 | $0.00032 | $0.00905 |
| Sonnet 5.5 | $0.00016 | $0.00453 |
| Haiku 4.5 | $0.00008 | $0.00226 |
Grade A, and why
sdcorejs-ai-agent 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 — 217 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.
SDCoreJS AI Agent
Execute an approved AI-agent plan as an authoring track. This skill produces application contracts, integration code, deterministic tests, and verification evidence. It does not install a provider runtime into this skill pack and it does not perform live provider calls.
Entry Gate
Require all of the following before writing:
- an immutable approved plan with
track: ai-agent; - its immutable approved spec and shared
approval_hash; - a valid plan
approval_hashwhose verified parent graph includes that spec; - an
agent_architectureblock that names oneengine_profile, onecapability_profile, target paths, trust boundaries, tool boundaries, persistence policy, approval policy, eval policy, and verification commands; - explicit user selection of sequential or parallel execution through
sdcorejs-execute-plan.
If any item is absent, ambiguous, stale, or hash-invalid, stop and return to the
owning workflow gate. Do not infer a profile from prose after plan approval.
Create and verify approved spec/plan identity only through
../../_refs/shared/approved-artifact.mjs; do not use a track-local hash scheme.
When a legacy portable handoff names these values approved_spec_hash and
approved_plan_hash, each value must equal the corresponding shared
approval_hash; the aliases do not authorize an independent hash contract.
Shared Protocols
Read ../../_refs/shared/runtime-protocols.md, ../../_refs/shared/system-registry.json,
and ../../_refs/ai-agent/manifest.json. Apply
../../_refs/shared/artifact-lifecycle.md when .sdcorejs/** is written. Use
../../_refs/shared/repository-contract.mjs for repository ownership and
../../_refs/ai-agent/execution-identity.mjs for profile resolution, approved graph
verification, runtime approval fingerprints, downstream artifact identity, and
offline/live evidence classification.
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 a75b4026a63d
- 1mo ago First seen · 215 lines · 81 tokens per session scan A 2a66c893c5ff
sdcorejs-ai-agent is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 81 tokens to every session and 2,263 once invoked, about $0.0003 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-09-05.
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…