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 aka-kika/akakika-skills --skill project-folder-cleanupgit clone --depth 1 https://github.com/aka-kika/akakika-skillsWrote 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/aka-kika/akakika-skills/project-folder-cleanup)<a href="https://agentmods.dev/skills/aka-kika/akakika-skills/project-folder-cleanup"><img src="https://agentmods.dev/badge/skills/aka-kika/akakika-skills/project-folder-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/aka-kika/akakika-skills/project-folder-cleanup"><img src="https://agentmods.dev/badge/skills/aka-kika/akakika-skills/project-folder-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 167 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00087 | $0.01409 |
| Opus 5.5 | $0.00035 | $0.00564 |
| Sonnet 5.5 | $0.00017 | $0.00282 |
| Haiku 4.5 | $0.00009 | $0.00141 |
Grade A, and why
project-folder-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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Folder Cleanup
Remove regenerable clutter from a project folder without losing data. Every targeted path is copied into a backup first, documented in BACKUP.md, compressed into a zip archive, and only then removed from the project when explicitly confirmed.
When to Use
- Clean
node_modules, build folders, caches, or logs from a project - Reclaim disk space before archiving or zipping a repo
- Reset a project to a fresh-build state
- Tidy a workspace after switching branches or experiments
Do not use it for general file organization across the whole computer — that's out of scope for this skill.
Core Rules
- Backup before delete — no exceptions
- Scan and confirm — show paths and sizes; get approval before destructive steps
- Dry-run first — always run with
--dry-rununtil the plan is approved - Zip the backup — keep disk use small; retain the
.zip, drop uncompressed folder by default - Document everything —
BACKUP.mdinside the backup explains what, why, and how to restore
Read Safety Rules before every run.
Workflow
Step 1: Choose the project
Confirm the project root path. Do not run from $HOME unless the user explicitly wants home-level cleanup.
Step 2: Scan candidates
node scripts/scan-cleanup-candidates.mjs /path/to/project --json
Or human-readable:
node scripts/scan-cleanup-candidates.mjs /path/to/project
Review output with the user. Compare against Default Cleanup Targets. Add or remove paths based on user preference.
Step 3: Check git status
git -C /path/to/project status --short
Warn if targeted paths overlap with uncommitted work the user may care about.
Step 4: Dry-run backup + cleanup plan
node scripts/cleanup-with-backup.mjs --project /path/to/project --dry-run
Optional custom manifest:
node scripts/cleanup-with-backup.mjs \
--project /path/to/project \
--targets /tmp/cleanup-targets.json \
--dry-run
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 168 lines · 87 tokens per session scan A b7dd75ff4952
project-folder-cleanup is a skill published in the GitHub repository aka-kika/akakika-skills (11 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 1,409 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
peon-ping-toggle
Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session. Also handles config changes like volume, pack rotation, categories — any peon-ping setting.
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
getting-started
Interactive post-onboarding tour that adapts to whatever data exists (calendar, Granola, or none). Use right after onboarding, or when the user says 'show me around', 'how do I start'. Also use proactively when the vault is < 7 days old. Not for the initial setup itself; use setup.
resume-builder
Build resume and LinkedIn profile through guided interview.
diff-generate
Package one workflow — how you use Dex for a specific job — into a shareable DexDiff methodology doc. Use when the user says 'share how I do X', 'package this workflow'. Not for packaging your entire system; use diff-profile. Not for adopting someone else's; use diff-adopt.
dex-obsidian-setup
Turn on Obsidian mode and migrate the vault to wiki links. Use when the user says 'I use Obsidian', 'enable wiki links', 'make this work in Obsidian'. Not for connecting an external tool/API; use create-mcp/integrate-mcp.