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/seabbs/skills/code-cleanupnpx skills add seabbs/skills --skill code-cleanupgit clone --depth 1 https://github.com/seabbs/skillsWhat 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.00027 | $0.00715 |
| Opus 5 | $0.00014 | $0.00358 |
| Sonnet 5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
code-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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Directory Cleanup
Audit and tidy the ~/code/ directory.
Run from the home directory (~/).
Phase 1: Inventory
For every subdirectory in ~/code/ (including inside org folders), collect:
- Git remote (
git remote get-url origin, or "no-git") - GitHub org (parsed from remote URL)
- Repo type (R package = has
DESCRIPTION, Julia package = hasProject.toml, paper/grant = has.qmd/.tex/submission/, website = has_quarto.ymlwithout package files, org-config =.githubrepos, other) - Last commit date (
git log -1 --format="%ci") - Folder name vs remote name mismatch
- Worktrees (
git worktree listin each repo, flag any worktrees whose branch no longer exists on the remote)
Phase 2: Flag Problems
Report a table for each category:
Folder name mismatches
Local name differs from remote repo name (excluding .git suffix).
For .github repos, convention is {org}-.github.
Stale repos (no commits in 6+ months)
Include last commit date and whether it's owned by seabbs orgs or external.
Dead worktrees
Worktrees whose tracking branch no longer exists on the remote, or worktrees with no uncommitted changes that haven't been touched in 30+ days.
Repos not in their org folder
Any repo whose remote belongs to a known org (epinowcast, epiforecasts, EpiAware, nfidd, seabbs) but isn't inside the corresponding ~/code/{org}/ folder.
External repos (not owned by seabbs orgs)
Repos from other orgs/users cloned locally.
No-git directories
Directories with no git remote.
Phase 3: Propose Actions
For each flagged item, propose one of:
- rename: fix folder name to match remote
- move: move into correct org folder
- archive: move to
~/code/archive/ - delete: remove entirely (only for empty dirs or confirmed duplicates)
- clean-worktree: remove dead worktree
Phase 4: Execute (with confirmation)
Present the full action list and ask for confirmation before executing. Group actions by type (renames, moves, archives, deletes, worktree cleanup).
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 · 83 lines · 27 tokens per session scan A 8b0b1c999e3f
code-cleanup is a skill published in the GitHub repository seabbs/skills (5 stars, last pushed 8d ago), licensed MIT. It adds 27 tokens to every session and 715 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…