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 loopdive/js2 --skill scratch-cleanupgit clone --depth 1 https://github.com/loopdive/js2Wrote 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/loopdive/js2/scratch-cleanup)<a href="https://agentmods.dev/skills/loopdive/js2/scratch-cleanup"><img src="https://agentmods.dev/badge/skills/loopdive/js2/scratch-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/loopdive/js2/scratch-cleanup"><img src="https://agentmods.dev/badge/skills/loopdive/js2/scratch-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.01376 |
| Opus 5.5 | $0.00023 | $0.00550 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 159 lines · 57 tokens per session scan A 317f61ae1ad3
scratch-cleanup is a skill published in the GitHub repository loopdive/js2 (67 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 1,376 once invoked, about $0.0002 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-30.
Other skills, from other repositories
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.
triaging-merge-queue-failures
Decision procedure for a PR that failed or was removed from the Trunk merge queue: classify the kick (superseded by a newer commit, not mergeable, a gate that failed on a cancelled run, real failure, one-off flake, or repo-wide flaky/infra issue) and take the matching action (wait, hold and fix, requeue once, or…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
triage-contributor-pr
Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…