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 Pixel-Process-UG/superkit-agents --skill file-organizergit clone --depth 1 https://github.com/Pixel-Process-UG/superkit-agentsWrote 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/pixel-process-ug/superkit-agents/file-organizer)<a href="https://agentmods.dev/skills/pixel-process-ug/superkit-agents/file-organizer"><img src="https://agentmods.dev/badge/skills/pixel-process-ug/superkit-agents/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/pixel-process-ug/superkit-agents/file-organizer"><img src="https://agentmods.dev/badge/skills/pixel-process-ug/superkit-agents/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.00071 | $0.02806 |
| Opus 5.5 | $0.00028 | $0.01122 |
| Sonnet 5.5 | $0.00014 | $0.00561 |
| Haiku 4.5 | $0.00007 | $0.00281 |
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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Organizer
Overview
Design and maintain well-organized project structures that scale with team and codebase growth. This skill covers monorepo patterns, feature-based vs layer-based architecture, naming conventions, index/barrel files, configuration file placement, and documentation structure.
Apply this skill whenever a project's file organization needs to be established, audited, or restructured for clarity and scalability.
Multi-Phase Process
Phase 1: Assessment
- Audit current project structure and identify pain points
- Measure project size (file count, team size, feature count)
- Identify existing naming conventions and import patterns
- Catalog configuration file locations
- Check for circular dependencies or deep nesting
STOP — Do NOT propose a new structure without understanding the current state and its pain points.
Phase 2: Strategy Selection
- Choose organization strategy using decision table below
- Define naming conventions and file placement rules
- Plan barrel export boundaries
- Establish configuration file placement rules
- Document import ordering convention
STOP — Do NOT begin migration without documenting the target structure and getting team alignment.
Phase 3: Migration Planning
- Plan migration path for existing projects (incremental, not big-bang)
- Identify files that move and their new locations
- Map import changes required
- Create automated codemods where possible
- Define rollback plan if migration causes issues
STOP — Do NOT execute migration without verifying tests pass at each incremental step.
Phase 4: Execution and Validation
- Move one feature or module at a time
- Update imports using automated tools
- Verify tests pass after each move
- Remove old structure after complete migration
- Document conventions for team reference
Architecture Strategy Decision Table
| Project Size | Team Size | Recommendation | Why |
|---|---|---|---|
| < 20 files | 1-2 devs | Layer-based | Simple, low overhead |
| 20-100 files | 2-5 devs | Hybrid | Balance of simplicity and scalability |
| 100+ files | 5+ devs | Feature-based | Self-contained modules reduce conflicts |
| Multiple apps sharing code | Any | Monorepo | Shared packages with clear boundaries |
| Rapid prototype / MVP | 1-3 devs | Layer-based | Speed over structure, refactor later |
| Enterprise, multiple teams | 10+ devs | Feature-based + Monorepo | Team ownership per feature module |
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 · 390 lines · 71 tokens per session scan A 77f598736b36
file-organizer is a skill published in the GitHub repository Pixel-Process-UG/superkit-agents (3 stars, last pushed 7mo ago), licensed MIT. It adds 71 tokens to every session and 2,806 once invoked, about $0.0003 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
outlook-calendar
A skill for managing Microsoft Outlook and Microsoft 365 calendar events through a connected account.
cron
Use this skill only for scheduled or recurring tasks. Manage jobs with qwenpaw cron list/create/get/state/pause/resume/delete/run, and always pass --agent-id explicitly.
cron
A scheduling tool for running tasks at a future time or repeating them on a set schedule. It manages scheduled jobs such as reminders, checks, and reports.
to-tickets
Slice a spec or a ticket into tracer-bullet tickets with blocking edges, published through the repo's tracker: .specs/tickets/ .md by default.
to-spec
Turn the settled conversation into a spec (PRD), published through the repo's tracker: .specs/specs/ .md by default.
pm-init
Skill "pm-init" from wei63w/pm-manager, covering user input, outline, 1. scaffold, 2. lifecycle and type and 3. detect spec kit (required).