start

start is a command for coding agents from ncssm-robotics/ftc-claude. It costs 5 tokens per session (541 once invoked), scanned A, original, MIT.

A command for starting an initialized OpMode, a programmed operating mode for an educational robot. It checks the robot and dashboard connection before sending the start request.

In plain words
What is it for?
Use `/start` to run the selected OpMode after initialization and connection.
Why use it?
It avoids manual dashboard control and reports common problems such as a missing OpMode or disconnected robot.

Command

Install

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.

agentmods
npx agentmods add commands/ncssm-robotics/ftc-claude/start
Clone the repo
git clone --depth 1 https://github.com/ncssm-robotics/ftc-claude

Wrote 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.

agentmods badge for start

README.md
[![agentmods](https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/start.svg)](https://agentmods.dev/commands/ncssm-robotics/ftc-claude/start)
Your own site
<a href="https://agentmods.dev/commands/ncssm-robotics/ftc-claude/start"><img src="https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/start.svg" alt="Measured on agentmods" height="20"></a>
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 541 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00005 $0.00541
Opus 5 $0.00003 $0.00270
Sonnet 5 $0.00001 $0.00108
Haiku 4.5 $0.00001 $0.00054

Measured 5d ago against content hash b499360d2010, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

start 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 5d 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.

plugins/robot-dev/commands/start.md · 134 lines

What it actually says

Start Command

Starts the currently initialized OpMode.

Usage

/start

Process

When this command runs:

  1. Check OpMode is initialized:

    • Query dashboard for current state
    • Must be in INIT state
  2. Send start command via websocket:

    uv run scripts/panels_client.py start
    

    This sends the startActiveOpMode message.

  3. Update HUD:

    🤖 Connected (12.4V) │ TeleOp Main [RUNNING] │ 192.168.43.1
    

Expected Output

Starting OpMode...

  OpMode: TeleOp Main
  ✓ Started

  Status: TeleOp Main [RUNNING]

  Use /stop to stop the OpMode

Error Handling

No OpMode Initialized

/start

  ✗ No OpMode initialized

  Initialize an OpMode first:
    /opmodes         # List available OpModes
    /init "TeleOp"   # Initialize one
    /start           # Then start it

Already Running

/start

  ⚠ OpMode already running

  Current: TeleOp Main [RUNNING]

  To restart:
    /stop
    /init "TeleOp Main"
    /start

Not Connected

/start

  ✗ Robot not connected

  Run /connect first, then try again.

Dashboard Not Available

/start

  ✗ Cannot reach dashboard

  OpMode control requires Panels or FTC Dashboard.

  Alternative: Press the Start button on the Driver Station.

State Transitions

[INIT] → /start → [RUNNING]

The OpMode's start() method is called, then loop() begins executing.

Tips

Autonomous vs TeleOp

For Autonomous OpModes:

  • The OpMode runs until completion or /stop
  • Timer starts when you run /start

For TeleOp OpModes:

  • Gamepad input is active after /start
  • Runs until /stop or 2-minute timer

Quick Start Sequence

/init Auto Left
/start

Or with safety check:

/opmodes                  # See what's available
/init "Auto Left"         # Initialize
/start                    # Go!
Changes

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.

  1. 5d ago First seen · 134 lines · 5 tokens per session scan A b499360d2010

Subscribe to this mod's changes

start is a command published in the GitHub repository ncssm-robotics/ftc-claude (4 stars, last pushed 7mo ago), licensed MIT. It adds 5 tokens to every session and 541 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.