Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ncssm-robotics/ftc-claudenpx agentmods add commands/ncssm-robotics/ftc-claude/opmodesWrote 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/opmodes)<a href="https://agentmods.dev/commands/ncssm-robotics/ftc-claude/opmodes"><img src="https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/opmodes.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.1 | $0.00007 | $0.00745 |
| Opus 5 | $0.00003 | $0.00373 |
| Sonnet 5 | $0.00001 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
opmodes 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 6d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpModes Command
Lists all available OpModes on the connected robot.
Usage
/opmodes # List all OpModes
/opmodes --auto # List Autonomous only
/opmodes --teleop # List TeleOp only
Arguments
| Argument | Description |
|---|---|
--auto |
Show only Autonomous OpModes |
--teleop |
Show only TeleOp OpModes |
Process
When this command runs:
-
Check connection:
adb devices -
Query Panels via websocket:
uv run scripts/panels_client.py listThe script connects to
ws://192.168.43.1:8001/wsand requests the OpMode list. -
Parse and display results
Expected Output
Available OpModes
──────────────────────────────────────────────
Autonomous:
1. Auto Left
2. Auto Right
3. Auto Center
TeleOp:
4. TeleOp Main
5. TeleOp Practice
6. PID Tuner
To run an OpMode:
/init "TeleOp Main"
/start
Filtered Output
Autonomous Only
/opmodes --auto
Autonomous OpModes
──────────────────────────────────────────────
1. Auto Left
2. Auto Right
3. Auto Center
TeleOp Only
/opmodes --teleop
TeleOp OpModes
──────────────────────────────────────────────
1. TeleOp Main
2. TeleOp Practice
3. PID Tuner
Error Handling
Not Connected
/opmodes
✗ Robot not connected
Run /connect first, then try again.
Dashboard Not Available
/opmodes
✗ Cannot reach dashboard
The OpMode list requires a dashboard connection.
Check:
1. Robot Controller app is running
2. Panels (port 8001) or FTC Dashboard (port 8080) is enabled
Alternative: View OpModes on the Driver Station app
No OpModes Found
/opmodes
No OpModes found.
This could mean:
1. No code has been deployed yet (/deploy)
2. OpModes are missing @TeleOp or @Autonomous annotations
3. Build errors prevented OpMode registration
Tips
OpMode Naming
Good OpMode names:
Auto Left- Clear starting positionTeleOp Main- Primary teleopPID Tuner- Specific purpose
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.
- 6d ago First seen · 160 lines · 7 tokens per session scan A 26d2114b8f3e
opmodes is a command published in the GitHub repository ncssm-robotics/ftc-claude (4 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 745 once invoked, about $0.0000 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
compliance-matrix
Gestiona matriz de conformidad con estándares regulatorios (CE, FCC, UL, RoHS, ISO). Permite definir estándares, trackear estado de requisitos, vincular evidencia, identificar gaps y generar reportes de cumplimiento.
eol-report
EOL/EOS risk report — devices, OS versions, and firmware approaching or past end-of-life/end-of-support, prioritized by criticality.
cisco-catalyst-ta-setup
Configure and validate the Cisco Catalyst Add-on (TAciscocatalyst), including SD-WAN API/BFD, UTD and ZBFW syslog routing, Cyber Vision, ISE, Catalyst Center, and the beta IOS-XE CLI collector.
rvcsi-calibrate
Learn a v0 per-subcarrier baseline (mean amplitude) from a .rvcsi capture.
esp-harden
Harden and inspect ESP32 firmware for field failures, crashes, memory, and security.
pentest-wireless
You are an expert wireless security tester covering Wi-Fi, Bluetooth, and IoT radio protocols. For AUTHORIZED testing only.