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/log)<a href="https://agentmods.dev/commands/ncssm-robotics/ftc-claude/log"><img src="https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/log/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/commands/ncssm-robotics/ftc-claude/log"><img src="https://agentmods.dev/badge/commands/ncssm-robotics/ftc-claude/log.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.00000 | $0.00883 |
| Opus 5.5 | $0.00000 | $0.00353 |
| Sonnet 5.5 | $0.00000 | $0.00177 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
log 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log Command
View robot logs with FTC-relevant filtering.
Usage
/log # View recent logs
/log -f # Follow logs in real-time
/log --errors # Show only errors
/log --filter TeamCode # Filter by tag
/log --clear # Clear log buffer first
Arguments
| Argument | Description |
|---|---|
-f, --follow |
Continuous output (like tail -f) |
--errors |
Show only errors and exceptions |
--filter <tag> |
Filter to specific tag (e.g., TeamCode, RobotCore) |
--clear |
Clear log buffer before reading |
--since <time> |
Show logs from last N minutes (e.g., --since 5m) |
Process
When this command runs:
-
Check connection:
adb devices -
Clear buffer (if
--clear):adb logcat -c -
Run logcat with filters:
Default (FTC-relevant):
adb logcat -v time RobotCore:* FtcRobotController:* TeamCode:* AndroidRuntime:E *:SErrors only:
adb logcat -v time *:ECustom filter:
adb logcat -v time <TAG>:* *:S -
Format and colorize output:
- Errors: Red
- Warnings: Yellow
- Info: Default
- Debug: Gray
Output Format
Robot Logs (Ctrl+C to exit)
──────────────────────────────────────────────
12:34:56.789 [INFO] RobotCore: OpMode 'TeleOp Test' initialized
12:34:56.823 [INFO] TeamCode: Motor initialized
12:34:57.001 [WARN] RobotCore: Battery voltage: 11.8V
12:34:57.234 [INFO] TeamCode: Position: x=12.5, y=24.3
12:35:01.456 [ERROR] AndroidRuntime: FATAL EXCEPTION
java.lang.NullPointerException
at MyOpMode.loop(MyOpMode.java:45)
Common Filters
Your Code Only
/log --filter TeamCode
Hardware Issues
/log --filter RobotCore
Vision/Camera
/log --filter Limelight
/log --filter OpenCV
Crashes Only
/log --filter AndroidRuntime --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.
- 2mo ago First seen · 169 lines · 0 tokens per session scan A 584376e17287
log is a command published in the GitHub repository ncssm-robotics/ftc-claude (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 883 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
ee-review
Produce an EE decision document (escalating intervention ladder + binding constraints, cited and confidence-graded) for an analog/placement-blocked board.
cortex-m
Generate Cortex-M startup code or a linker script, configure a core subsystem, decode a fault, or add DWT timing.
debug-embedded
Attach a debugger, halt and inspect a target, decode fault registers, or configure ITM, SWO, or ETM trace.
gpu
Diagnose GPU health, discover bounded recipes, and collect typed numeric evidence without guessing from screenshots.
debug
A command-line debugging toolkit for embedded programs using J-Link or OpenOCD, tools that connect a computer to a microcontroller for inspection.
la
A command for capturing and decoding signals with a Saleae logic analyzer, a device that records electrical digital signals over time. It supports buses such as UART, SPI, and I2C, which are common ways chips communicate with peripherals.