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/loopdive/js2/scratch-cleanupnpx skills add loopdive/js2 --skill scratch-cleanupgit clone --depth 1 https://github.com/loopdive/js2What 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.00057 | $0.01376 |
| Opus 5 | $0.00028 | $0.00688 |
| Sonnet 5 | $0.00011 | $0.00275 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
scratch-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 2d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scratch Cleanup
Find all leaked ad-hoc dev scratch files in /workspace, verify they are not legitimate WIP, move them into the gitignored .tmp/ folder, and verify .gitignore patterns cover future leaks.
When to use
git statusin /workspace shows 20+ untrackedcheck-*,debug-*,test-*,probe-*,run-*files- Starting a new session and inheriting leaked scratch from prior dev agents
- After an OOM or crash where dev worktrees may have spilled files into the main workspace
- Before running
/compactor/session-wrapupto keep the committed state clean
Step 1: Verify /workspace/main
pwd && git branch --show-current
Must be /workspace on main.
Step 2: Survey untracked non-plan files
git status --short | grep '^??' | grep -vE '(plan/|\.claude/|test262$|components/)' | head -60
Patterns to sweep (all represent ad-hoc debug/probe scripts):
Root level:
check-*.ts,check-*.mtsdebug-*.ts,debug-*.mtsrun-*.ts,run*.mjs,run-test*.mjstest-*-debug.ts,test-*-main.ts,test-on-main*.tstest-src*.ts,test-wat*.tstest-throws-*.ts,test-full-wat-*.ts,test-disposable-*.ts,test-pr-*.ts
Under tests/:
tests/probe-*.test.tstests/test-*-debug.test.ts,tests/test-*-probe.test.tstests/scope-close-*-debug.test.tstests/regression-check.test.tstests/test-type-mismatch.test.tstests/test-pr*-regressions.test.tstests/*-debug*.test.ts
Preserve (do NOT move):
tests/issue-NNNN*.test.ts— likely real WIP from a dev; check PR queue before movingplan/**— planning docs.claude/memory/**— team memory
Step 3: Check for false positives
Before moving anything, verify the file is NOT referenced by an open PR:
for f in <SUSPECT_FILES>; do
if gh pr list --limit 20 --json files --jq ".[] | select(.files[]?.path==\"$f\") | .number"; then
echo " KEEP: $f referenced by open PR"
else
echo " MOVE: $f"
fi
done
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.
- 2d ago First seen · 159 lines · 57 tokens per session scan A 317f61ae1ad3
scratch-cleanup is a skill published in the GitHub repository loopdive/js2 (59 stars, last pushed 2d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,376 once invoked, about $0.0003 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-30.
Other skills, from other repositories
migrate-oxfmt
Guide for migrating a project from Prettier or Biome to Oxfmt. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's formatter from Prettier or Biome to Oxfmt.
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
insta-snapshots
Guide for working with and updating insta snapshot tests in Oxc without terminal interaction.
performance-lint-rules
Performance review guidance for Oxc linter rule implementations. Use only when reviewing Rust rule code under crates/oxclinter/src/rules/ or when explicitly auditing those rules for performance improvements.
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
babel-docs
Babel 7.x/8.x — plugins, presets, config, @babel/core, parser, traverse, types, CLI, preset-env.