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-cleanupgit 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-cleanup)<a href="https://agentmods.dev/skills/sdcorejs/sdcorejs-agent/sdcorejs-cleanup"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-cleanup/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-cleanup"><img src="https://agentmods.dev/badge/skills/sdcorejs/sdcorejs-agent/sdcorejs-cleanup.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.00092 | $0.02208 |
| Opus 5.5 | $0.00037 | $0.00883 |
| Sonnet 5.5 | $0.00018 | $0.00442 |
| Haiku 4.5 | $0.00009 | $0.00221 |
Grade A, and why
sdcorejs-cleanup 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 — 179 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.
Cleanup
Shared protocols and ownership
Read ../../_refs/shared/runtime-protocols.md, then apply Project Context Preflight
v2 from ../../_refs/shared/project-context.md. Read repository instructions and
current changes; resolve the target repository and explicitly bounded scope.
Use ../../_refs/shared/tasklist.md for non-trivial work and
../../_refs/shared/user-choice-prompt.md before a decision. Keep reusable source
English; localize runtime prose and preserve exact paths, hashes and commands.
This utility owns filesystem hygiene, not an implementation track. Source
refinement belongs to sdcorejs-simplify; tests and data teardown belong to
sdcorejs-test; quality assessment belongs to sdcorejs-review; rewriting or
consolidating docs belongs to sdcorejs-documentation. A candidate requiring
imports, public API or code changes is a finding/handoff to its existing owner.
For disk-space or dependency-size requests, select storage-audit and load
../../_refs/cleanup/storage-audit.md.
It inventories explicit local roots by metadata without reading VM contents
or hashing millions of files. Whole-machine inspection includes accessible
fixed local volumes, not network/removable drives unless requested. Analysis
does not authorize cache cleaning, dependency pruning or Docker changes.
Load ../../_refs/cleanup/workflow.md for the
runtime scope, offer and task-tail contract. Use the single engine
../../_refs/cleanup/cleanup-engine.mjs
and its pure policy
../../_refs/cleanup/cleanup-contract.mjs.
The storage helpers are read-only observation tools, not a second mutation
engine. Do not implement another cleanup executor or run git clean -fdx.
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 · +18 lines 0d603c231eab
- 25d ago First seen · 161 lines · 92 tokens per session scan A fa25b62d5c19
sdcorejs-cleanup is a skill published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 92 tokens to every session and 2,208 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-10-10.
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…