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 commands/coltonbearden/carrel/taggit 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/tag)<a href="https://agentmods.dev/commands/coltonbearden/carrel/tag"><img src="https://agentmods.dev/badge/commands/coltonbearden/carrel/tag.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.00019 | $0.00423 |
| Opus 5 | $0.00010 | $0.00211 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
tag 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 today.
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
Handle this tagging request: $ARGUMENTS
Run the carrel CLI via Bash. Map the user's request onto these real subcommands of carrel tag (verify with carrel tag --help if unsure — never invent flags). Tags live in the desk db (.carrel/carrel.db under the global --root, default cwd):
carrel [--root DIR] tag add PATH TAGS... # tag a file (registers it in the desk db if needed)
carrel [--root DIR] tag rm PATH TAGS... # remove tags (unknown tags/files are a quiet no-op)
carrel [--root DIR] tag ls [PATH] # tags of PATH, or every tag with its file count
carrel [--root DIR] tag find TAGS... # files carrying ALL of the given tags
- Choose the subcommand from intent: "tag X as invoice" →
add, "what's tagged urgent" →find, "untag" →rm, "what tags exist" →ls. findreturns paths relative to the desk root; ANDs multiple tags.- If the user's desk is elsewhere, put
--root DIRbeforetag.
Report what changed (or list the results) conversationally. Tags combine well with /carrel-inspect:search --tag for filtered full-text search — mention that when relevant.
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.
- today Changed 38bfd78387e2
- 4d ago First seen · 25 lines · 19 tokens per session scan A 7cc1e44842ac
tag is a command published in the GitHub repository coltonbearden/carrel (1 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 423 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-31.
Other commands, from other repositories
meeting-notes
Summarize a meeting transcript into structured notes with decisions, action items, and follow-ups.
save-prompt
Generalize the current discussion into a reusable prompt and save it as a file.
feature-flow-w
Complete git worktree workflow orchestration (GitHub/GitLab/Forgejo) - worktree, branch, issue, commit.
meeting-end
Stop the meeting Voice Memo, draft notes, and prepare follow-up email to attendees.
meeting-setup
Prepare for a meeting by syncing attendees to Contacts, creating prep reminders, and updating Calendar alerts.
feature-flow
Complete git workflow orchestration (GitHub/GitLab/Forgejo) - branch, issue, commit.