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-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/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-review"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-review.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.00083 | $0.06549 |
| Opus 5.5 | $0.00033 | $0.02620 |
| Sonnet 5.5 | $0.00017 | $0.01310 |
| Haiku 4.5 | $0.00008 | $0.00655 |
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 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 — 503 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.
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.
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 a8c1d028cecd
- 1mo ago Changed · +5 lines bda9b6037018
- 2mo 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 15d ago), licensed MIT. It adds 83 tokens to every session and 6,549 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-08-31.
Other skills, from other repositories
sync-bridge
Reviews and guides Chromium Sync Model API (DataTypeSyncBridge) implementations, including DataTypeStore persistence and forwards/backwards compatibility for sync specifics. Use when implementing or reviewing a DataTypeSyncBridge subclass, DataTypeStore usage, sync metadata persistence, conflict resolution, or…
sync-model-processor
Reviews changes to Chromium Sync model internals in components/sync/model/, including ClientTagBasedDataTypeProcessor, ClientTagBasedRemoteUpdateHandler, ProcessorEntity, ProcessorEntityMetadata, and ProcessorEntityTracker. Use when modifying or reviewing processor state transitions, entity metadata tracking, conflict…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
gsd-ns-review
Invoke this Pi skill with /skill:gsd-ns-review.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…