Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/commands/ncssm-robotics/ftc-claude/stop)<a href="https://agentmods.dev/commands/ncssm-robotics/ftc-claude/stop"><img src="https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/stop.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.00005 | $0.00602 |
| Opus 5 | $0.00003 | $0.00301 |
| Sonnet 5 | $0.00001 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
stop 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stop Command
Stops the currently running OpMode.
Usage
/stop
Process
When this command runs:
-
Check OpMode is running:
- Query dashboard for current state
- Should be in
RUNNINGstate
-
Send stop command via websocket:
uv run scripts/panels_client.py stopThis sends the
stopActiveOpModemessage. -
Update HUD:
🤖 Connected (12.4V) │ TeleOp Main [STOPPED] │ 192.168.43.1
Expected Output
Stopping OpMode...
OpMode: TeleOp Main
✓ Stopped
Status: TeleOp Main [STOPPED]
To run again:
/init "TeleOp Main"
/start
Error Handling
No OpMode Running
/stop
⚠ No OpMode currently running
Nothing to stop.
Not Connected
/stop
✗ Robot not connected
Run /connect first, then try again.
Dashboard Not Available
/stop
✗ Cannot reach dashboard
OpMode control requires Panels or FTC Dashboard.
Alternative: Press the Stop button on the Driver Station.
State Transitions
[RUNNING] → /stop → [STOPPED]
The OpMode's stop() method is called:
- Motors are stopped
- Resources are cleaned up
- OpMode becomes inactive
After Stopping
After /stop, you can:
-
Run the same OpMode again:
/init "Same OpMode" /start -
Switch to a different OpMode:
/init "Different OpMode" /start -
Check logs for issues:
/log --errors
Tips
Emergency Stop
If the robot is behaving unexpectedly, /stop immediately stops the OpMode.
For a hardware emergency:
- Press the physical E-Stop button on the robot
- Or power off the robot
Graceful Shutdown
Your OpMode's stop() method is called when /stop runs. Use it to:
@Override
public void stop() {
// Set motors to zero
leftMotor.setPower(0);
rightMotor.setPower(0);
// Close any resources
camera.close();
}
Viewing What Happened
After stopping, check the logs:
/log --errors
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.
- 5d ago First seen · 150 lines · 5 tokens per session scan A 665e2f572909
stop 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 602 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
observe
部屋を能動的に観察する。3つの基本ブロックを自由に選びながらループし、受動的なスナップショットではなく発見のある観察を行う。.
model
Check if an AI model fits on your GPU before downloading.
tapeout
Produce a complete, fab-ready export bundle for a routed board — or refuse loudly. Superset of /kct:manufacturing-readiness: runs the three sign-off pre-gates, then adds a BOM part-number-resolution gate, a per-rule warning-review gate (assembly-affecting warnings block unless explicitly acknowledged), schematic +…
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.