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.
git clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/rules/danielvm-git/bigpowers/organize-workspace)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/organize-workspace"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/organize-workspace/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/rules/danielvm-git/bigpowers/organize-workspace"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/organize-workspace.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.00093 | $0.01999 |
| Opus 5.5 | $0.00037 | $0.00800 |
| Sonnet 5.5 | $0.00019 | $0.00400 |
| Haiku 4.5 | $0.00009 | $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 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.
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 — 164 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.
- 1mo ago First seen · 164 lines · 93 tokens per session scan C 1a1852cfde04
organize-workspace is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 93 tokens to every session and 1,999 once invoked, about $0.0004 per session on Opus 5.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-09-03.
Other cursor rules, from other repositories
pudo-core
Core PUDO workflow rules for all Cursor agent work.
agent-efficiency
Agent-mode tool-call efficiency. Cuts the largest hidden cost in modern AI IDEs — wasted tool calls and oversized context windows.
vscode
VS Code: settings, extensions, workspace config.
dynamic-confirmed-list
Enforces automatic creation and management of a dynamic confirmed list for explicit, structured, and precise interactions between Cursor AI and users.
reply-tracker
Reply Tracker (also known as Reply Zero) lets the user which emails need a reply for them and those they're awaiting a reply on. It updates the labels for the thread automatically in Gmail.
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…