file-butler

file-butler is a skill for Claude Code from Caprista/KarvyLoop. It costs 68 tokens per session (1,787 once invoked), scanned A, original, MIT.

A file-organization method that first inventories folders, previews proposed changes, and waits for your approval before moving anything.

In plain words
What is it for?
Use it to sort personal folders, plan safe moves, protect files before deletion, and review an organization proposal before applying it.
Why use it?
It reduces the risk of files being misplaced or deleted based on guesses. It follows your own filing rules and provides a record of what was done.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to sort personal folders, plan safe moves, protect files before deletion, and review an organization proposal before applying it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/caprista/karvyloop/file-butler
Install

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.

Any agent
npx skills add Caprista/KarvyLoop --skill file-butler
Clone the repo
git clone --depth 1 https://github.com/Caprista/KarvyLoop

Made for: Claude Code.

Wrote 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.

agentmods badge for file-butler

README.md
[![agentmods](https://agentmods.dev/badge/skills/caprista/karvyloop/file-butler.svg)](https://agentmods.dev/skills/caprista/karvyloop/file-butler)
Your own site
<a href="https://agentmods.dev/skills/caprista/karvyloop/file-butler"><img src="https://agentmods.dev/badge/skills/caprista/karvyloop/file-butler.svg" alt="Measured on agentmods" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,787 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.01787
Opus 5 $0.00034 $0.00894
Sonnet 5 $0.00014 $0.00357
Haiku 4.5 $0.00007 $0.00179

Measured 8d ago against content hash 3a0c319901a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

file-butler 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 8d 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.

karvyloop/system_skills/file-butler/SKILL.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

File Butler (system template)

Files are not data rows. A wrong query can be re-run; a file moved to the wrong place — or deleted — costs the human real time and sometimes real work. So this method optimizes for trust before tidiness: everything is previewed, nothing is deleted without an explicit human decision, and the plan is grounded in the user's own filing rules, not a textbook ideal. This skill is a method, not a canned answer.

The accountability rule

You (atom) answer to the role; the role answers to the human. A folder that looks tidy but lost or hid one file spends trust you cannot get back. When in doubt, propose and ask — never act on a guess about where something belongs or whether it is junk.

The method library (pick per situation, name your pick in the proposal)

  • PARA (Tiago Forte, Building a Second Brain): sort by actionability, not by topic — Projects (active, has a goal and an end), Areas (ongoing responsibilities), Resources (topics of interest), Archives (everything inactive). Default for Documents. Rule of thumb: if it has a deadline it's a Project; if you must maintain it forever it's an Area.
  • GTD inbox-zero (David Allen, Getting Things Done): treat Downloads and Desktop as inboxes — transit stations, never storage. Each item gets one touch-and-decide pass: file it to its real home, archive it, or propose it for deletion. An inbox is "done" when it is empty, not when it is sorted.
  • Johnny.Decimal (johnnydecimal.com): number areas and categories (11.03 …) so every file has exactly one home and a stable, quotable address. Offer it only when the user wants a rigid, numbered tree — it is strict by design.
  • Naming rules (standard research-data-management practice, e.g. university RDM guides): YYYY-MM-DD ISO date prefix for time-ordered files; no spaces or special characters (-/_ instead); content words over generic ones (2026-07-04-loan-contract-draft not document(3) copy); versions as v01, v02 suffixes — never final, final2, REAL_final.
  • Duplicate detection: same size is a hint; identical content hash (e.g. sha1sum/md5sum via run_command) is the fact. Browser-created name (1).ext copies are candidates only until hashes match. Duplicates are proposed for deletion (with which copy to keep and why) — never auto-deleted. Full decision order (size → hash → content-difference, with thresholds and the versions-vs-duplicates distinction) is in references/filing-methods.md.
  • Archiving by last use (hot/cold): untouched for ~180 days and not on the never-touch list → propose moving to Archives/<year>/. The timer is a default, not a law — finance/legal files follow the user's rules, not the clock. Archive moves are reversible by design; deletions never ride along in an archive batch. Completed projects archive as a whole folder.
  • Per-type conventions (defaults; the user's rules outrank): screenshots → monthly archive folders; installers → deletion candidates ~30 days after install; finance documents → never auto-delete at any age; camera photos → keep original filenames. Full table in references/filing-methods.md.

Read the full file on GitHub · 124 lines

Files

What ships with it

2 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.

Changes

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.

  1. 8d ago First seen · 124 lines · 68 tokens per session scan A 3a0c319901a8

Subscribe to this mod's changes

file-butler is a skill published in the GitHub repository Caprista/KarvyLoop (16 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 1,787 once invoked, about $0.0003 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.

Related

Other skills, from other repositories