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/nodealchemy/powernode-platform/cleanupnpx skills add nodealchemy/powernode-platform --skill cleanupgit clone --depth 1 https://github.com/nodealchemy/powernode-platformWhat 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.00000 | $0.00424 |
| Opus 5 | $0.00000 | $0.00212 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 50 lines · 0 tokens per session scan A a281872b9485
cleanup is a skill published in the GitHub repository nodealchemy/powernode-platform (2 stars, last pushed 3d 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
good-first-issue-batch
File a batch of contributor-ready GitHub issues from the seeds backlog, re-verifying every candidate against HEAD first so no dead issue reaches a contributor. Activate for prompts like "file some good first issues", "open a batch of GFIs", "publish backlog issues to GitHub", "find contributor-ready work", or after an…
seeds-issue-audit
Audit and triage open Seeds (sd) issues — find which can be closed, auto-close high-confidence completed ones, and report borderline cases. Activate for prompts like "audit open issues", "which seeds issues can be closed", "clean up the issue tracker", "triage the seeds backlog".
os-eco-dep-sync
Bump warren onto the latest published @os-eco/ versions across package.json + bun.lock and the Dockerfile CLI pins, then run the gates and open a PR. Use when checking if warren is on the newest burrow/plot/canopy/seeds/mulch/sapling.
release
Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.
warren-dogfood-pipeline
Full prioritize → dispatch → shepherd → track pipeline against the live warren instance. Audits the seeds backlog around a focus theme, dispatches the surviving issues to warren agents one at a time, babysits the resulting PRs to merge (update-branch, conflict-repair runs, auto-merge), and closes the loop in the…
canvas
Display HTML content on connected Mayros nodes (Mac app, iOS, Android).