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.
git clone --depth 1 https://github.com/coltonbearden/carrelWrote 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/commands/coltonbearden/carrel/organize)<a href="https://agentmods.dev/commands/coltonbearden/carrel/organize"><img src="https://agentmods.dev/badge/commands/coltonbearden/carrel/organize/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/commands/coltonbearden/carrel/organize"><img src="https://agentmods.dev/badge/commands/coltonbearden/carrel/organize.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.00026 | $0.00836 |
| Opus 5.5 | $0.00010 | $0.00334 |
| Sonnet 5.5 | $0.00005 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
organize 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.
What it actually says
Organize the folder the user asked about: $ARGUMENTS
Run the carrel CLI via Bash. Map the user's request onto the real flags in the --help block below (regenerated from the CLI by scripts/sync_plugins.py; if the installed carrel organize --help differs, trust the installed version — never invent flags):
Usage: carrel organize [OPTIONS] DIRECTORY
Plan (default) or perform (--apply) sorting DIRECTORY's files.
Only files directly inside DIRECTORY are considered; subdirectories and hidden files stay put.
Existing files are never overwritten — colliding names get a -1, -2, … suffix. JSON output is a
list of {src, dest, action} ('move' planned, 'moved' executed, 'skip').
--apply refuses (exit 2) when it would move files git is tracking, where a new path breaks
imports, tests and history; --allow-tracked overrides. Untracked files inside a repository are
fine.
Options:
--by [type|date|exif-date] Grouping: 'type' -> pdf/, images/ (jpg, png, ico), data/ (json, xml,
csv), docs/ (md, txt, html), mail/ (eml, mbox); 'date' -> YYYY/MM from
mtime; 'exif-date' -> YYYY/MM from EXIF DateTimeOriginal, mtime
fallback (images only; other files are skipped). [default: type]
--into CATEGORY=DIR Override a type category's destination subdir, e.g. --into images=pics
(only with --by type; repeatable).
--apply / --dry-run Execute the moves. Default is a dry-run that only prints the plan.
--allow-tracked Move files even when they are tracked by git (see the description).
--force Deprecated spelling of --allow-tracked; warns when it bypasses the
guard.
--json Machine-readable JSON output.
--help Show this message and exit.
Note: --json is a global flag and may come before the subcommand.
--by type(default): subdirs like pdf/, images/, data/, docs/;date: YYYY/MM from mtime;exif-date: EXIF DateTimeOriginal with mtime fallback (images only).--into CATEGORY=DIR: override a category's subdirectory name (type mode only; categories: pdf, images, data, docs — e.g.--into images=pics). Repeatable.- Dry-run is the default. ALWAYS run the dry-run first, show the user the planned moves
{src, dest, action}, and only re-run with--applyafter they confirm (or when they already asked to "actually move" things). Collisions get-1,-2suffixes; nothing is ever overwritten.
If the installed carrel predates organize (its --help reports no such command), say so and offer manual organization (list files with carrel inspect/Glob, propose moves) instead of guessing flags.
Report afterwards: how many files moved where, and any collisions renamed.
Requires the carrel CLI on PATH. If carrel is not found, tell the user to install it with uv tool install carrel (see the repo's INSTALL notes), or run it as uv run carrel ... from the carrel repo root.
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 Changed · +3 lines 9dcb4196cad6
- 1mo ago Changed · +4 lines 2bcf80d67ca9
- 1mo ago Changed · +20 lines 4c44f3e9cf74
- 1mo ago Changed c57de321d967
- 1mo ago First seen · 26 lines · 26 tokens per session scan A d7df416e6bd1
organize is a command published in the GitHub repository coltonbearden/carrel (2 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 836 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
review-resume
Comprehensive PM resume review against 10 best practices — structure, impact metrics, keywords, and actionable feedback.
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
stop
Gracefully close the Vibe Squad tmux session from inside Chrono.
amp-download
Command "amp-download" from agentmessaging/claude-plugin, covering /amp-download, usage, arguments, options and examples.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
maestro-companion
Quick execution for small tasks — minimal run lifecycle (start + done) with evidence recording. Full LLM capability, scoped to mechanically clear tasks.