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/connect)<a href="https://agentmods.dev/commands/ncssm-robotics/ftc-claude/connect"><img src="https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/connect.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.00000 | $0.00951 |
| Opus 5 | $0.00000 | $0.00476 |
| Sonnet 5 | $0.00000 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
connect 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 7d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connect Command
Establishes a connection to your FTC robot.
Usage
/connect # Connect via WiFi (default)
/connect --usb # Connect via USB cable
/connect --ip 10.0.0.1 # Connect to custom IP
Arguments
| Argument | Description |
|---|---|
--wifi |
Connect via WiFi (default) |
--usb |
Connect via USB cable |
--ip <address> |
Custom robot IP (default: 192.168.43.1) |
--port <port> |
Custom ADB port (default: 5555) |
WiFi Connection (Default)
When connecting via WiFi:
-
Check network:
- Verify computer is on robot's WiFi network
- Robot network is usually
TEAMNUMBER-RC
-
Connect ADB:
adb connect 192.168.43.1:5555 -
Verify:
adb devices
Expected Output
Connecting to robot via WiFi...
Connecting to 192.168.43.1:5555...
✓ Connected!
Device: Control Hub
Serial: 1234567890ABCDEF
Run /deploy to upload your code
USB Connection
When connecting via USB:
-
Check USB:
adb devices -
If device found, enable wireless:
adb tcpip 5555 -
Get device IP and connect:
adb shell ip route | grep wlan0 adb connect <ip>:5555
Expected Output
Connecting to robot via USB...
✓ USB device found
✓ Enabled TCP/IP mode
✓ Connected wirelessly
You can now unplug the USB cable.
Robot IP: 192.168.43.1
Run /deploy to upload your code
Error Handling
No Robot Found
Connecting to robot via WiFi...
✗ Cannot reach 192.168.43.1
Troubleshooting:
1. Is the robot powered on?
2. Are you on the robot's WiFi network?
- Look for a network named "TEAMNUMBER-RC"
- Your current network: "Home-WiFi" ← wrong network!
3. Is the robot's WiFi enabled?
- Check Driver Station settings
Try: /connect --usb (use a USB cable instead)
USB Device Not Found
Connecting to robot via USB...
✗ No USB device found
Troubleshooting:
1. Connect a USB cable from your computer to the Control Hub
2. Use the USB-C port on the Control Hub (not the phone port)
3. Try a different cable (some cables are charge-only)
4. On Windows: Install USB drivers (see /doctor)
After connecting, run /connect --usb again
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.
- 7d ago First seen · 171 lines · 0 tokens per session scan A 0e09b0a1d160
connect is a command published in the GitHub repository ncssm-robotics/ftc-claude (4 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 951 tokens. 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
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.
put
Upload file to reMarkable (converts markdown to PDF).