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-architecturegit 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-architecture)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-architecture"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-architecture/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-architecture"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-architecture.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.00096 | $0.02030 |
| Opus 5.5 | $0.00038 | $0.00812 |
| Sonnet 5.5 | $0.00019 | $0.00406 |
| Haiku 4.5 | $0.00010 | $0.00203 |
Grade A, and why
sdcorejs-architecture 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 — 216 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.
Architecture
Shared protocols
Read ../../_refs/shared/runtime-protocols.md, ../../_refs/shared/project-context.md,
../../_refs/shared/artifact-lifecycle.md, ../../_refs/shared/decision-coverage.md, and
../../_refs/sdlc/architecture.md. Resolve tracks, artifact roots/kinds, repository
roles, and ownership from ../../_refs/shared/system-registry.json. Use
../../_refs/shared/architecture-contract.mjs as the only architecture gate/context,
ownership, path, lifecycle-handoff, revision, and write-scope authority. Reuse
../../_refs/shared/approved-artifact.mjs for approval identity; never create a
second hash implementation.
Purpose and boundary
This skill converts a verified approved spec into the smallest durable set of
architecture decisions that independent implementation units must share. It is
the conditional gate between sdcorejs-spec and sdcorejs-plan.
Route adjacent intents without stealing them:
| User intent | Owner |
|---|---|
| Map or explain the current architecture | sdcorejs-explore |
| Review/audit the current or proposed architecture | sdcorejs-review (architecture) |
| Design architecture from this approved spec | sdcorejs-architecture |
| Explore or compare open-ended system designs | sdcorejs-brainstorming |
| Produce file/task implementation steps | sdcorejs-plan |
Architecture does not own file-by-file order, task sequencing, production code, executed test evidence, release decisions, or convention persistence.
Preconditions
- An immutable approved spec and its complete
spec_contextare available. verifyApprovedArtifactGraphverifies that exact spec before drafting.- Stable requirement/decision/assumption/invariant records are available.
- Semantic repository topology is resolved independently of the current working directory.
- The request is no longer open-ended. Otherwise route to brainstorming.
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 893ff93155d5
- 2mo ago First seen · 214 lines · 96 tokens per session scan A 490b183cf49f
sdcorejs-architecture is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 96 tokens to every session and 2,030 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…