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/danielvm-git/bigpowers/organize-workspacenpx skills add danielvm-git/bigpowers --skill organize-workspacegit clone --depth 1 https://github.com/danielvm-git/bigpowersWhat 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.00098 | $0.02005 |
| Opus 5 | $0.00049 | $0.01002 |
| Sonnet 5 | $0.00020 | $0.00401 |
| Haiku 4.5 | $0.00010 | $0.00200 |
Grade C, and why
organize-workspace scanned grade C with 1 finding 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Prefer `fd` / `ripgrep` / `find`** in that order; avoid blind `rm -rf` on vague globs. How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organize Workspace
HARD GATE — HARD GATE — Workspace structure must reflect domain structure. If the codebase feels disorganized, flag it. Disorganization != 'just a style thing;' it is a signal of domain misalignment.
Principles
- Read-only first: inventory and size (
du,ls -la) before any change. - Never delete or move without a numbered list and explicit user approval (item-level or "approve all").
- Prefer
fd/ripgrep/findin that order; avoid blindrm -rfon vague globs. - Do not touch
.git/,node_modules/,venv/,.env*, or SSH keys; flag them only if the user asked about them. - Confirm prompts in the user's language if they are not writing in English.
1. Establish scope
- Default: current project root (where the user is working) or the path they name.
- Record OS (macOS vs Linux) for ignore patterns (e.g.
.DS_Store).
2. Classify candidates (scan)
Group findings under these buckets:
| Bucket | Examples | Typical action |
|---|---|---|
| Logs & temp | *.log, logs/, tmp/, temp/, *.pid |
Delete after confirm |
| Build / cache | dist/, build/, .next/, coverage/, .turbo/ |
Delete if rebuildable |
| Package caches | root .cache/, __pycache__/ |
Offer delete |
| Stray drafts | root-level *.md named draft, scratch, temp |
User picks: delete, move to specs/, or keep |
| Duplicate / dump dirs | old/, backup/, copy/, *_backup |
List + ask |
Use quick size hints: du -sh per top-level dir; sort large items first.
3. Assets & data (organize, not only delete)
If the user wants organization:
- Propose a single convention, e.g.:
assets/— images, fonts, static mediadata/— JSON, CSV, fixtures, samplesspecs/— all planning and domain documents
- For each cluster of loose files, suggest one target path and a short rationale.
- Use git-aware moves when in a repo:
git mvif tracked; otherwisemvand report. - Never move secrets or production DB dumps into
docs/or publicassets/.
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.
- 3d ago First seen · 165 lines · 98 tokens per session scan C 7b5bbaf006a0
organize-workspace is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 26d ago), licensed MIT. It adds 98 tokens to every session and 2,005 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
re0-upgrade
Bring your installed paperthin skills up to the full current catalog in one step: retire what's been renamed, add every skill you don't have yet, and refresh the rest, all shown and confirmed before anything changes.
behavior-design
Use when a goal must be converted into a repeatable behavior, cue, SOP, review cadence, and identity-aligned reinforcement.
daily-okr
Use when planning or closing a daily knowledge-compounding cycle across input, cognition, wiki, behavior, creativity, output, and feedback.
sounding-board
Opinionated rubber duck. Reflects the user's thinking back in plain language, flags gaps, and offers concrete suggestions -- one exchange at a time. Use when the user says "bounce this off you", "think with me", "sounding board", "talk this through", "what do you think", or wants collaborative feedback on an idea…
context-manager
Smart context selection engine. Analyzes the current task, consults the Project Graph, and returns only the documents and skills needed. Prevents context window overflow by loading minimum relevant information.
raycast-automator
Use when the user asks to automate a task with Raycast, build a Raycast extension, create a Raycast script command, or mentions Raycast in the context of building something. Triggers on: "automate X with Raycast", "build a Raycast extension", "create a raycast script", "make a raycast command", or any task where…