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/doctor)<a href="https://agentmods.dev/commands/coltonbearden/carrel/doctor"><img src="https://agentmods.dev/badge/commands/coltonbearden/carrel/doctor/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/doctor"><img src="https://agentmods.dev/badge/commands/coltonbearden/carrel/doctor.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.00031 | $0.00500 |
| Opus 5.5 | $0.00012 | $0.00200 |
| Sonnet 5.5 | $0.00006 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
doctor 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
Check the carrel environment: $ARGUMENTS
Run the carrel CLI via Bash. The command takes no arguments beyond --json (the --help block below is regenerated from the CLI by scripts/sync_plugins.py; if the installed carrel doctor --help differs, trust the installed version):
Usage: carrel doctor [OPTIONS]
Report environment health: adapters found, versions, per-command capability.
Options:
--json Machine-readable JSON output.
--help Show this message and exit.
Always run carrel --json doctor and read the report:
product.version,python: what is installed.adapters[]: every optional binary carrel knows about —found,path,version, and aninstall_hintwhen absent, already written for the platformdoctorran on — relay it rather than composing your own.commands[]: per carrel command astatusofok,degraded(works with reduced power;optionalbinaries missing) orunavailable(arequiresbinary or Python extra is missing), plusmissingand anote.icc_dirs,tesseract_langs: color-profile directories found and OCR languages installed.
Answer the user's actual question: if they asked "can I OCR / convert docx / narrate a PDF", quote that command's status and the exact install hint for whatever is missing rather than dumping the whole table. If they asked generally, summarize: N commands ok / degraded / unavailable, then the two or three most valuable missing binaries with their hints. doctor is read-only and always exits 0.
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 scan B → A ee91f3e4dd27
- 1mo ago First seen · 34 lines · 31 tokens per session scan B 7c93f425206d
doctor is a command published in the GitHub repository coltonbearden/carrel (2 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 500 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-09-05.
Other commands, from other repositories
verify-upgrade
Verify Spring Boot project upgrade readiness with parallel multi-skill analysis.
local
Command "local" from getsentry/toolkit, covering examples, start the server and tail events (default), run your app with the local server auto-enabled, use a custom port and only show errors and logs (filter out transactions).
poly-check
Lint and check formatting with poly — apply no fixes; summarize findings and drift.
debug-files
Command "debug-files" from getsentry/toolkit, covering examples, inspect a debug information file (auto-detects the format), bundle jvm sources with a debug id, exclude additional directories and output as json.
release
Command "release" from getsentry/toolkit, covering examples, list releases (auto-detect org), list releases in a specific org, view release details and create and finalize a release.
perf-profile.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.