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 agentmods add commands/ncssm-robotics/ftc-claude/initgit 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/init)<a href="https://agentmods.dev/commands/ncssm-robotics/ftc-claude/init"><img src="https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/init.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 | $0.00007 | $0.00748 |
| Opus 5 | $0.00003 | $0.00374 |
| Sonnet 5 | $0.00001 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
init 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 4d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init Command
Selects and initializes an OpMode on the robot.
Usage
/init "TeleOp Main" # Initialize by exact name
/init TeleOp # Initialize by partial match
/init 3 # Initialize by number (from /opmodes list)
Arguments
| Argument | Description |
|---|---|
<opmode-name> |
Name of OpMode to initialize (full or partial) |
Process
When this command runs:
-
Check connection:
adb devices -
Find OpMode:
- If number given, look up from recent
/opmodeslist - If name given, find matching OpMode (partial match OK)
- If multiple matches, prompt user to choose
- If number given, look up from recent
-
Send init command via websocket:
uv run scripts/panels_client.py init "TeleOp Main"This sends the
initOpModemessage with the OpMode name. -
Update HUD:
🤖 Connected (12.4V) │ TeleOp Main [INIT] │ 192.168.43.1
Expected Output
Initializing OpMode...
✓ Found: "TeleOp Main"
✓ Initialized
Status: TeleOp Main [INIT]
Next: /start to begin running
Partial Matching
The command supports partial name matching:
/init teleop
Found multiple matches:
1. TeleOp Main
2. TeleOp Practice
3. TeleOp Debug
Which one? (enter number): 1
✓ Initialized "TeleOp Main"
Error Handling
Not Connected
/init TeleOp
✗ Robot not connected
Run /connect first, then try again.
OpMode Not Found
/init MyOpMode
✗ OpMode "MyOpMode" not found
Available OpModes:
- TeleOp Main
- TeleOp Practice
- Auto Left
Try: /opmodes to see full list
Dashboard Not Available
/init TeleOp
✗ Cannot reach dashboard
OpMode control requires Panels or FTC Dashboard.
Alternative: Use the Driver Station app to init the OpMode.
Already Running
/init TeleOp
⚠ OpMode "Auto Left" is currently running
Stop it first:
/stop
Then init the new OpMode.
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.
- 4d ago First seen · 166 lines · 7 tokens per session scan A 3be7bdb18604
init 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 748 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.