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/nweii/agent-stuff/file-namingnpx skills add nweii/agent-stuff --skill file-naminggit clone --depth 1 https://github.com/nweii/agent-stuffWrote 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/nweii/agent-stuff/file-naming)<a href="https://agentmods.dev/skills/nweii/agent-stuff/file-naming"><img src="https://agentmods.dev/badge/skills/nweii/agent-stuff/file-naming.svg" alt="Measured on agentmods" 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 | $0.00048 | $0.00706 |
| Opus 5 | $0.00024 | $0.00353 |
| Sonnet 5 | $0.00010 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
file-naming 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rename Files
Analyze files and propose intelligent renames based on content type and metadata. Provide: a single file path, list of file paths, or folder path.
Naming Conventions
Transactional/Periodic Documents
Repetitive transactions (orders, receipts, invoices, appointments):
- Format:
YYYY-MM-DD Category Type - Details.extension - Example:
2025-06-13 Amazon Order 123-456 - USB Cable.pdf - Include: dates, entity names, order/invoice numbers, item descriptions
Periodic documents (statements, bills, forms):
- Format:
YYYY-MM Type - Entity.extension - Example:
2025-06 Bank Statement - Chase Checking.pdf - Example:
2023-12 W2 - Acme Corp.pdf
Ongoing agreements (contracts, policies):
- Format:
YYYY-MM Type - Entity.extension - Example:
2025-01 Service Agreement - Internet Provider.pdf
Appointments/visits:
- Format:
YYYY-MM-DD Type - Provider/Location.extension - Example:
2025-06-13 Dental Visit - Dr Johnson.pdf
Creative/Project Files
Date as supplementary (photos, projects, creative work):
- Format:
Description - Date.extensionorDescription - Context Date.extension - Example:
Vacation Photos - Hawaii 2025.jpg - Example:
Website Redesign - Draft 2025-06.pdf - Example:
Company Logo 2025.png
Evergreen content (manuals, references):
- Format:
Type - Name/Description.extension - Example:
Product Manual - Widget Pro.pdf
Key Principles
- ISO 8601 dates: YYYY-MM-DD (specific dates) or YYYY-MM (monthly/annual)
- Date placement: Start for time-critical sorting; end for contextual info
- Remove: Technical metadata (1080p, WEB-DL), problematic characters (
:*?"<>|#%&) - Keep: Scannable and sortable filenames
Process
- Analyze files using OCR, text extraction, vision analysis, filename patterns
- Build the complete rename plan before taking any action
- Validate the plan: if any file cannot be mapped to a destination name, stop and report — do not proceed with partial results
- Validate the plan: confirm no two files share a destination name — if any collision exists, stop and report
- Present preview table: "Original Filename" | "New Filename" (show up to 15 files if many present; note any that couldn't be analyzed)
- Wait for confirmation before executing
- Execute using no-clobber semantics — never overwrite an existing file; if a collision occurs at execution time, halt immediately
What ships with it
1 file 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.
- 4d ago First seen · 73 lines · 48 tokens per session scan A 0eee0e0b4184
file-naming is a skill published in the GitHub repository nweii/agent-stuff (8 stars, last pushed 15d ago), licensed MIT. It adds 48 tokens to every session and 706 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…