Borrowing it
Nothing to install: this file belongs to nodealchemy/powernode-platform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nodealchemy/powernode-platform/develop/.claude/skills/cleanup/SKILL.mdgit clone --depth 1 https://github.com/nodealchemy/powernode-platformWrote 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/nodealchemy/powernode-platform/cleanup)<a href="https://agentmods.dev/skills/nodealchemy/powernode-platform/cleanup"><img src="https://agentmods.dev/badge/skills/nodealchemy/powernode-platform/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/nodealchemy/powernode-platform/cleanup"><img src="https://agentmods.dev/badge/skills/nodealchemy/powernode-platform/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.00000 | $0.00424 |
| Opus 5.5 | $0.00000 | $0.00170 |
| Sonnet 5.5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
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 2mo 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.
What it actually says
/cleanup — Codebase Cleanup
Run codebase cleanup and validation scripts. Wraps existing automation scripts into a single command.
Usage
/cleanup # Run all cleanup checks
/cleanup console # Remove console.log statements
/cleanup patterns # Run pattern validation audit
/cleanup colors # Fix hardcoded color violations
/cleanup imports # Convert relative imports to path aliases
/cleanup quick # Quick pattern check only
Workflow
Determine Scope
Based on the argument (default: all), run the appropriate scripts:
| Argument | Script | Description |
|---|---|---|
all |
All scripts below in order | Full cleanup pass |
console |
./scripts/cleanup-all-console-logs.sh |
Remove console.log from frontend |
patterns |
./scripts/pattern-validation.sh |
Full pattern audit (colors, imports, types) |
colors |
./scripts/fix-hardcoded-colors.sh |
Replace hardcoded colors with theme classes |
imports |
./scripts/convert-relative-imports.sh |
Convert relative imports to @/ aliases |
quick |
./scripts/quick-pattern-check.sh |
Fast pattern check |
Execution
- Run the selected script(s) from the project root
- Capture output and report results
- If
allmode, run in this order:./scripts/cleanup-all-console-logs.sh./scripts/fix-hardcoded-colors.sh./scripts/convert-relative-imports.sh./scripts/pattern-validation.sh
- Report summary of changes made and any remaining issues
Post-Cleanup Verification
After cleanup, run quality gates:
cd frontend && npx tsc --noEmit # Verify no TypeScript errors introduced
If TypeScript errors are introduced by cleanup, fix them before reporting completion.
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.
- 2mo ago First seen · 50 lines · 0 tokens per session scan A a281872b9485
cleanup is a skill published in the GitHub repository nodealchemy/powernode-platform (4 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 424 tokens. 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
migrate-doctor
A diagnostic and repair workflow for a broken or incomplete migration of an agent second-brain installation. It checks older and newer service layouts, identifies why the upgrade script failed, and guides the system toward version 3.0.
memory-informed-debug
Debug with working memory -- before diagnosing, recall prior root causes and known-good diagnostic procedures; when a root cause is confirmed, capture it immediately. Use whenever debugging a non-trivial failure.
graft
This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from graft before grepping or reading source files.
governed-bug-fix
Fix a bug through GraQle's governed workflow — investigate with the knowledge graph, check blast radius, plan, generate a reviewed diff, and teach the outcome back to the graph. Use when fixing bugs in a repository that has a GraQle knowledge graph (graqle.json / graqle.yaml present) and the GraQle MCP server…
gaia-steward-observe
Observe the repository with every registered Gaia Steward detector and report what each one actually saw, without changing anything. Use for "/gaia-steward-full --observe", "what is Steward seeing", "scan the repo for maintenance debt", or as the first phase of a full Steward run. Distinguishes actively observed…
graphlens-navigation
Navigate the code graph using graphlens MCP tools instead of reading files or grepping. Use when asked: "what calls X", "what breaks if I change X", "who uses this function", "what does this function depend on", "impact analysis", "find callers", "find references", "what implements/extends X", "what's in this file"…