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 skills add ncssm-robotics/ftc-claude --skill robot-devgit 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/skills/ncssm-robotics/ftc-claude/robot-dev)<a href="https://agentmods.dev/skills/ncssm-robotics/ftc-claude/robot-dev"><img src="https://agentmods.dev/badge/skills/ncssm-robotics/ftc-claude/robot-dev/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/skills/ncssm-robotics/ftc-claude/robot-dev"><img src="https://agentmods.dev/badge/skills/ncssm-robotics/ftc-claude/robot-dev.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.00048 | $0.00859 |
| Opus 5.5 | $0.00019 | $0.00344 |
| Sonnet 5.5 | $0.00010 | $0.00172 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
robot-dev 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 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.
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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FTC Robot Development Tools
Commands and guidance for the FTC robot development workflow. Designed to help rookies get up and running quickly.
Quick Start
1. Check Your Setup
/doctor
This checks if ADB is installed and helps you install it if needed.
2. Connect to Robot
/connect
Connects to your robot via WiFi (default) or USB.
3. Build and Deploy
/build # Compile your code
/deploy # Build and install to robot
4. Debug
/log # View robot logs
/log --errors # View only errors
5. Control OpModes
/opmodes # List available OpModes
/init TeleOp # Initialize an OpMode
/start # Start the OpMode
/stop # Stop the OpMode
Available Commands
| Command | Description |
|---|---|
/doctor |
Check environment setup (ADB, connection) |
/connect |
Connect to robot via WiFi or USB |
/build |
Compile robot code |
/deploy |
Build and deploy to robot |
/log |
View filtered robot logs |
/opmodes |
List available OpModes |
/init |
Initialize an OpMode |
/start |
Start the initialized OpMode |
/stop |
Stop the running OpMode |
Connection Basics
WiFi Connection (Recommended)
- Power on your robot
- Connect your computer to the robot's WiFi network (usually
TEAMNUMBER-RC) - Run
/connect
USB Connection
- Connect USB cable from computer to Control Hub
- Run
/connect --usb
Common Issues
See TROUBLESHOOTING.md for solutions to:
- "ADB not found"
- "Cannot connect to robot"
- "Deploy failed"
Environment Setup
See ADB_SETUP.md for platform-specific ADB installation instructions.
Status HUD
When connected, the status line shows:
🤖 Connected (12.4V) │ TeleOp Test [INIT] │ 192.168.43.1
See HUD.md for configuration options.
Anti-Patterns
Don't: Skip /doctor on a new machine
# BAD - Jump straight to connecting
/connect # "ADB not found" error
# GOOD - Check environment first
/doctor # Identifies missing dependencies
/connect # Now it works
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 154 lines · 48 tokens per session scan A ab7ceec0b509
robot-dev is a skill published in the GitHub repository ncssm-robotics/ftc-claude (5 stars, last pushed 9mo ago), licensed MIT. It adds 48 tokens to every session and 859 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when the device is managed by Catalyst Center and you want its…