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/ncssm-robotics/ftc-claudeWrote 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/ncssm-robotics/ftc-claude/doctor)<a href="https://agentmods.dev/commands/ncssm-robotics/ftc-claude/doctor"><img src="https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/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/ncssm-robotics/ftc-claude/doctor"><img src="https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/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.00015 | $0.01083 |
| Opus 5.5 | $0.00006 | $0.00433 |
| Sonnet 5.5 | $0.00003 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade D, and why
doctor scanned grade D with 3 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 2mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Linux: `sudo apt install android-tools-adb` Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- macOS/Linux: `curl -LsSf https://astral.sh/uv/install.sh | sh` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(adb:*), Bash(uv:*), Bash(which:*), Bash(command:*), Bash(brew:*), Bash(curl:*), Bash(ping:*), Read, Glob How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doctor Command
Diagnoses your FTC development environment and helps fix issues.
Usage
/doctor # Check environment
/doctor --fix # Attempt automatic fixes
What It Checks
-
ADB Installation
- Is
adbcommand available? - What version is installed?
- Is
-
uv (Python runner)
- Is
uvcommand available? - Required for OpMode control and future plugins
- Is
-
Robot Reachability
- Can we ping the robot (192.168.43.1)?
- Is the robot's ADB port accessible?
-
Gradle Setup
- Does
gradlewexist in the project? - Is it executable?
- Does
-
Project Structure
- Is this an FTC project (has TeamCode)?
- Is local.properties configured?
Process
When this command runs:
-
Detect platform (macOS, Linux, Windows)
-
Check ADB:
command -v adb adb versionIf missing, show platform-specific install instructions:
- macOS:
brew install android-platform-tools - Linux:
sudo apt install android-tools-adb - Windows: Download from developer.android.com
- macOS:
-
Check uv:
command -v uv uv --versionIf missing, show platform-specific install instructions:
- macOS/Linux:
curl -LsSf https://astral.sh/uv/install.sh | sh - Windows:
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
- macOS/Linux:
-
Check robot connection:
ping -c 1 -W 2 192.168.43.1 adb devices -
Check Gradle:
ls -la gradlew ./gradlew --version -
Check project:
- Look for
TeamCode/directory - Check
local.propertiesexists
- Look for
Output Format
FTC Development Environment Check
Platform: macOS 14.0
ADB:
✓ Installed (version 35.0.1)
✓ In PATH
uv (Python runner):
✓ Installed (version 0.4.x)
✓ In PATH
Robot Connection:
✓ Network reachable (192.168.43.1)
✓ ADB connected
Gradle:
✓ gradlew found
✓ Executable
Project:
✓ TeamCode directory found
✓ local.properties configured
Summary: 10/10 checks passed
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.
- 2mo ago First seen · 193 lines · 15 tokens per session scan D d41207a346ea
doctor is a command published in the GitHub repository ncssm-robotics/ftc-claude (5 stars, last pushed 9mo ago), licensed MIT. It adds 15 tokens to every session and 1,083 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
ee-review
Produce an EE decision document (escalating intervention ladder + binding constraints, cited and confidence-graded) for an analog/placement-blocked board.
cortex-m
Generate Cortex-M startup code or a linker script, configure a core subsystem, decode a fault, or add DWT timing.
debug-embedded
Attach a debugger, halt and inspect a target, decode fault registers, or configure ITM, SWO, or ETM trace.
gpu
Diagnose GPU health, discover bounded recipes, and collect typed numeric evidence without guessing from screenshots.
debug
A command-line debugging toolkit for embedded programs using J-Link or OpenOCD, tools that connect a computer to a microcontroller for inspection.
la
A command for capturing and decoding signals with a Saleae logic analyzer, a device that records electrical digital signals over time. It supports buses such as UART, SPI, and I2C, which are common ways chips communicate with peripherals.