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 claude-office-skills/skills --skill file-organizergit clone --depth 1 https://github.com/claude-office-skills/skillsWrote 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/claude-office-skills/skills/file-organizer)<a href="https://agentmods.dev/skills/claude-office-skills/skills/file-organizer"><img src="https://agentmods.dev/badge/skills/claude-office-skills/skills/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/claude-office-skills/skills/file-organizer"><img src="https://agentmods.dev/badge/skills/claude-office-skills/skills/file-organizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00012 | $0.01722 |
| Opus 5 | $0.00006 | $0.00861 |
| Sonnet 5 | $0.00002 | $0.00344 |
| Haiku 4.5 | $0.00001 | $0.00172 |
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 12d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Organizer
Intelligently organize and rename files based on their content and metadata.
Overview
This skill helps you:
- Analyze file contents to determine categorization
- Suggest folder structures
- Generate consistent naming conventions
- Identify and handle duplicates
- Create organization systems
How to Use
Analyze Files
"Analyze these files and suggest how to organize them"
"What category does this file belong to?"
"Suggest a better filename for this document"
Organize
"Create a folder structure for my project files"
"Organize my downloads folder"
"Sort these invoices by vendor and date"
Naming Conventions
Recommended Formats
Documents
YYYY-MM-DD_Category_Description_v1.ext
Example: 2026-01-29_Contract_ClientName_NDA_v1.pdf
Images
YYYY-MM-DD_Event/Project_Description_NNN.ext
Example: 2026-01-29_ProductLaunch_HeroImage_001.png
Invoices/Receipts
YYYY-MM-DD_Vendor_Amount_InvoiceNumber.ext
Example: 2026-01-29_Adobe_149.99_INV-12345.pdf
Meeting Notes
YYYY-MM-DD_MeetingType_Topic.ext
Example: 2026-01-29_TeamSync_Q1Planning.md
Naming Rules
- Use underscores or hyphens, not spaces
- Start with date for chronological sorting
- Include key identifiers (client, project, type)
- Add version numbers for iterations
- Keep names concise but descriptive
Folder Structures
Personal Documents
📁 Documents
├── 📁 Admin
│ ├── 📁 Finance
│ │ ├── 📁 Invoices
│ │ ├── 📁 Receipts
│ │ └── 📁 Tax
│ ├── 📁 Insurance
│ └── 📁 Legal
├── 📁 Work
│ ├── 📁 Projects
│ ├── 📁 Reports
│ └── 📁 Meetings
├── 📁 Personal
│ ├── 📁 Health
│ ├── 📁 Education
│ └── 📁 Travel
└── 📁 Archive
└── 📁 [Year]
Project-Based
📁 ProjectName
├── 📁 01_Planning
│ ├── 📁 Requirements
│ ├── 📁 Proposals
│ └── 📁 Research
├── 📁 02_Design
│ ├── 📁 Mockups
│ ├── 📁 Assets
│ └── 📁 Specs
├── 📁 03_Development
│ ├── 📁 Source
│ ├── 📁 Tests
│ └── 📁 Documentation
├── 📁 04_Deliverables
│ └── 📁 [Version]
├── 📁 05_Admin
│ ├── 📁 Contracts
│ ├── 📁 Invoices
│ └── 📁 Communications
└── 📁 Archive
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.
- 12d ago First seen · 281 lines · 12 tokens per session scan A 79c4efac6bf6
File Organizer is a skill published in the GitHub repository claude-office-skills/skills (465 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 1,722 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
structure-checker
Analyses a draft article's structural architecture — paragraph order, logical flow, redundancies, and pacing — and returns a diagnostic report with specific reordering, cutting, or restructuring recommendations.
file-manager
A file and folder management helper for organizing files on a computer.
email-management
Inbox management workflow — triage, batching, folder strategy, and inbox zero maintenance.
clean-messy-notes-to-action-items
Turn unstructured notes into action items with owners, deadlines, decisions, and unresolved follow-ups.
code-architecture
Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion"…
GCP Naming And Labeling
GCP naming convention and mandatory labels — resource-type abbreviations, region codes, and owner/cost-center/environment/workload labels for cost attribution.