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/catalog)<a href="https://agentmods.dev/commands/coltonbearden/carrel/catalog"><img src="https://agentmods.dev/badge/commands/coltonbearden/carrel/catalog/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/catalog"><img src="https://agentmods.dev/badge/commands/coltonbearden/carrel/catalog.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.00038 | $0.01245 |
| Opus 5.5 | $0.00015 | $0.00498 |
| Sonnet 5.5 | $0.00008 | $0.00249 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade A, and why
catalog 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handle this desk-catalog request: $ARGUMENTS
Run the carrel CLI via Bash. carrel catalog is a group with export, import and status; map the user's request onto the real subcommands and flags in the --help blocks below (regenerated from the CLI by scripts/sync_plugins.py; if the installed carrel catalog --help differs, trust the installed version — never invent flags):
Usage: carrel catalog [OPTIONS] COMMAND [ARGS]...
Export, import and check the desk catalog (tags, notes, meta in .carrel/carrel.db).
Options:
--json Machine-readable JSON output.
--help Show this message and exit.
Commands:
export Export every file's tags, notes and meta fields as JSON (files with at least one).
import Merge FILE (a `catalog export` document) into the desk under --root.
status Report the desk db: schema version, row counts, and stale index entries.
Usage: carrel catalog export [OPTIONS]
Export every file's tags, notes and meta fields as JSON (files with at least one).
Document: {"schema", "product", "version", "exported", "root", "files": [{"path": <root-relative>,
"tags": [...sorted], "notes": [{"created", "body"}], "meta": [{"key", "value", "kind",
"source"}]}]}, sorted by path — byte-identical across runs apart from "exported". Without -o the
document itself is printed (always JSON); with -o a short summary is printed instead. Exit 4 when
no desk db exists.
Options:
-o, --out FILE Write the catalog to FILE instead of stdout (refuses to overwrite without
--force).
--force Overwrite an existing --out file.
--json Machine-readable JSON output.
--help Show this message and exit.
Usage: carrel catalog import [OPTIONS] FILE
Merge FILE (a `catalog export` document) into the desk under --root.
Tags already present are kept (INSERT OR IGNORE); notes are deduplicated on (file, created, body);
meta fields take the document's value (counted only when it changed), so importing the same
document twice adds nothing. Entries whose path does not exist under the root are counted in
skipped_missing and not created. Exit 4 for unreadable/invalid JSON or a "schema" newer than this
build supports. JSON output: {tags_added, notes_added, meta_set, files_touched, skipped_missing,
tags_removed, notes_removed, meta_removed, skipped_outside}.
Options:
--replace Delete ALL existing tags, notes and fields first, then import (prints what was
removed).
--json Machine-readable JSON output.
--help Show this message and exit.
Usage: carrel catalog status [OPTIONS]
Report the desk db: schema version, row counts, and stale index entries.
JSON: {schema_version, db_path, counts: {files, docs, tags, notes, meta}, stale: {changed,
missing, unindexed}, examples: {changed, missing, unindexed} (up to 5 paths each)}. Always exit 0
(it is a report); exit 4 when no .carrel/carrel.db exists under --root.
Options:
--json Machine-readable JSON output.
--help Show this message and exit.
Note: --json and --root are global flags and go before catalog (carrel --json --root DIR catalog status).
- export: writes the tags and notes of every tagged/annotated file as one JSON document (
{schema, product, version, exported, root, files: [{path, tags, notes}]}, paths root-relative, deterministic apart fromexported). Without-othe document goes to stdout; with-o FILEa summary is printed. Never pass--forceunless the user wants an existing file replaced. - import FILE: merges a
catalog exportdocument into the desk under--root. Idempotent — existing tags are kept and notes are deduplicated, so importing twice adds nothing. Paths that don't exist under the root are counted inskipped_missing.--replacedeletes ALL existing tags and notes first — treat it likededupe --apply: only after explicit confirmation. - status:
{schema_version, db_path, counts: {files, docs, tags, notes}, stale: {changed, missing, unindexed}, examples}. Always exit 0 as a report; exit 4 when no desk db exists.
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 457a0d089e04
- 1mo ago First seen · 87 lines · 38 tokens per session scan A 40a7bb0c290f
catalog is a command published in the GitHub repository coltonbearden/carrel (2 stars, last pushed 4d ago), licensed MIT. It adds 38 tokens to every session and 1,245 once invoked, about $0.0002 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-05.
Other commands, from other repositories
review-resume
Comprehensive PM resume review against 10 best practices — structure, impact metrics, keywords, and actionable feedback.
vs-stop
Gracefully close the Vibe Squad tmux session from inside Chrono.
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…
create-entity
Create a new entity in the domain model using MDL.
ops
Weekly operations loop — triage the inquiry inbox, advance the CRM pipeline, sweep open PRs across repos, and surface the content plan. Loads the ops skill.
amp-download
Command "amp-download" from agentmessaging/claude-plugin, covering /amp-download, usage, arguments, options and examples.