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-testgit 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-test)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-test"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-test/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-test"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-test.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.00086 | $0.02905 |
| Opus 5.5 | $0.00034 | $0.01162 |
| Sonnet 5.5 | $0.00017 | $0.00581 |
| Haiku 4.5 | $0.00009 | $0.00291 |
Grade A, and why
sdcorejs-test 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 — 244 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.
Test Track
Purpose and ownership
Own test planning, test authoring, safe execution, coverage matrices, UAT cases,
RED-first TDD, authenticated runner evidence, and UI capture verification.
sdcorejs-debug owns root-cause investigation and production bug fixes.
sdcorejs-documentation owns guide prose and image placement. This skill must
not invoke Git, call sdcorejs-git, install dependencies, or start/modify a
runtime unless the current request explicitly authorizes that exact action.
Shared protocols
- Read
../../_refs/shared/runtime-protocols.md, then../../_refs/shared/tasklist.mdfor non-trivial work and../../_refs/shared/persona.mdwhen present. - Apply Project Context Preflight v2 from
../../_refs/shared/project-context.md. Current request, files, diff, requirements, command output, and test failures override stored context. Missing or stale summary never blocks testing and does not authorize a refresh. Continue with targeted reads or a scoped code map. - Apply
../../_refs/shared/artifact-lifecycle.mdwhenever evidence or documentation assets are created; returnartifact_context. - Apply
../../_refs/shared/user-choice-prompt.mdbefore presenting approval or mode choices. - Localize runtime-facing prose to the user's language. Keep schema keys, commands, identifiers, and canonical source English.
Step 1 - Classify the action
Pick exactly one public action:
test_action |
Boundary |
|---|---|
run-only |
Discover and run existing commands; no edits. |
write-tests |
Edit scoped tests/fixtures; discovery only, no run. |
write-and-run |
Edit scoped tests, then run focused discovered commands. |
test-plan-readonly |
Read-only risk, case, and command plan. |
coverage-audit |
Read-only current coverage and requirement gaps unless tests are requested. |
uat-cases |
Produce requested UAT cases/checklists; no source implementation. |
tdd-red |
Write the smallest failing test and prove RED; no production code. |
tdd-cycle |
RED, minimal GREEN implementation, then refactor and verify. |
failing-output-triage |
Explain/classify sanitized output without edits. |
debug-handoff |
Stop and transfer fix/root-cause work to sdcorejs-debug. |
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 3d7508222835
- 2mo ago First seen · 242 lines · 86 tokens per session scan A 9e3e1a9e0ade
sdcorejs-test is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 86 tokens to every session and 2,905 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
nw-test-design-mandates
Design mandates for acceptance tests - hexagonal boundary, business language abstraction, user journey completeness, pure function extraction, 3 Pillars (domain language / chained narrative / production composition), and the layered ATD discipline (Universe-bound assertion, layer-dependent PBT mode, two-tier…
nw-bdd-methodology
BDD patterns for acceptance test design - Given-When-Then as a language-neutral specification style, scenario writing rules, realization in the project's incumbent native scenario syntax (Python pytest-bdd binding labelled), anti-patterns, and living documentation.
nw-test-organization-conventions
Test directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.
testing
Testing: TDD, E2E, preferred patterns, test-value audits, verification, agent testing.
nw-ad-critique-dimensions
Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof.
nw-spike
A bounded probe of one product, visual-experience or technical uncertainty; returns evidence to its owner without starting a wave or promoting code automatically.