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 GoogilyBoogily/googilyboogily-claude-power-tools --skill file-organizergit clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/file-organizer)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/file-organizer"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/file-organizer/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/googilyboogily/googilyboogily-claude-power-tools/file-organizer"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/file-organizer.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.00045 | $0.01258 |
| Opus 5.5 | $0.00018 | $0.00503 |
| Sonnet 5.5 | $0.00009 | $0.00252 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
file-organizer 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Organizer
Design clean, domain-separated directory hierarchies using research-backed methodologies. Audit existing structures, detect anti-patterns, propose reorganizations, and execute migrations with user confirmation.
Input
$ARGUMENTS — the target directory path to organize. If empty, ask using AskUserQuestion.
Safety Rules
- NEVER move, rename, or delete files without explicit user confirmation
- NEVER touch source code directories (src/, lib/, app/) unless specifically asked
- NEVER modify file contents — only move/rename files and create directories
- Always present a complete migration plan and wait for approval before executing
- Create a backup reference (list of original paths) before any bulk operation
Core Principles
- MECE (Mutually Exclusive, Collectively Exhaustive) — every file belongs in exactly one place, every file has a place
- Primary Home Rule — each file gets one canonical location; use symlinks or references for cross-cutting concerns
- Single Axis Per Level — each directory level sorts by one dimension only (by type, by domain, by stage — never mixed)
- Depth Limit — max 3-4 levels deep; flatten if deeper
- Goldilocks Breadth — 5-12 top-level categories; fewer than 5 means categories are too broad, more than 12 means they need grouping
Decision Script: Where Does This File Go?
For any file, answer these questions in order. The first match wins:
- Is it configuration? (dotfiles, .json/.yaml config, CI files) →
config/or project root - Is it documentation? (.md, .rst, .adoc about how/why/what) →
docs/subtree (apply Diataxis within) - Is it a template or generator? (scaffolding, boilerplate, cookiecutter) →
templates/ - Is it test data or fixtures? (sample inputs, mocks, snapshots) → alongside tests or
fixtures/ - Is it a static asset? (images, fonts, icons, media) →
assets/subdivided by type - Is it a script or tool? (build scripts, dev utilities, one-off scripts) →
scripts/ortools/ - Is it domain content? → categorize by domain using PARA or Diataxis (see Phase 2)
What ships with it
3 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 · 130 lines · 45 tokens per session scan A 72dfe14a3528
file-organizer is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 1,258 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.