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-reviewnpx skills add sdcorejs/sdcorejs-agent --skill sdcorejs-reviewgit 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-review)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-review"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-review.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.06317 |
| Opus 5 | $0.00042 | $0.03159 |
| Sonnet 5 | $0.00017 | $0.01263 |
| Haiku 4.5 | $0.00008 | $0.00632 |
Grade A, and why
sdcorejs-review 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 4d 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 — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review (profile + dimension aware)
Purpose
One read-only review skill for code, architecture, security, performance, and
accessibility. It classifies both track and track_profile before loading
track-specific references so plain Angular, NestJS, Next.js, and general
projects are not reviewed against SDCoreJS framework conventions they do not
use.
sdcorejs-review must not edit source code. Direct user-requested review is
strict read-only by default and must not silently write .sdcorejs artifacts or
auto-run sdcorejs-repair-loop. Repair belongs to sdcorejs-repair-loop after
an explicit user or finish-gate choice.
Resolve track and its durable review_profile from
_refs/shared/system-registry.json, then validate context/findings with
_refs/shared/review-contract.mjs. Do not maintain a separate first-class
track enum in this skill.
Shared Protocols
Read _refs/shared/runtime-protocols.md. Apply
_refs/shared/artifact-lifecycle.md only when the user explicitly chooses to
persist the report. Read _refs/shared/decision-coverage.md; preserve
decision_coverage and goal_backward_review, and report drift, missing task
or evidence mappings, invariant gaps, or unresolved critique blockers without
renumbering or repairing the approved records.
Preserve architecture_context and the exact conditional gate from the
approved plan. Architecture review compares changed boundaries, ownership,
public contracts, profile blocks, and validation evidence with approved
INV-*; a stale/missing/mutated required context is a finding, never permission
to rewrite architecture or conventions.
Read _refs/shared/validation-map.md; preserve the approved validation_map
and report drift from mapped cases or current evidence without rewriting rows.
When to use
- After a track executor finishes a batch and the finish gate selected review.
- Before merging a feature branch.
- User says "review code", "security review", "performance review", "review a11y", "architecture review", "comprehensive audit", "full review", "scored review", or localized equivalents.
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.
- 4d ago First seen · 496 lines · 83 tokens per session scan A 5fd200c06259
sdcorejs-review is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 18d ago), licensed MIT. It adds 83 tokens to every session and 6,317 once invoked, about $0.0004 per session on Opus 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
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…