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 panelsgit 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/panels)<a href="https://agentmods.dev/skills/ncssm-robotics/ftc-claude/panels"><img src="https://agentmods.dev/badge/skills/ncssm-robotics/ftc-claude/panels/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/panels"><img src="https://agentmods.dev/badge/skills/ncssm-robotics/ftc-claude/panels.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.00038 | $0.00761 |
| Opus 5.5 | $0.00015 | $0.00304 |
| Sonnet 5.5 | $0.00008 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
panels 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Panels Dashboard
Panels (by Lazar/ByteForce) is a web-based dashboard for FTC robots providing telemetry, graphs, and live configuration.
Quick Start
Add dependency in TeamCode/build.gradle:
implementation "com.bylazar:fullpanels:1.0.6"
Access dashboard at 192.168.43.1:8001 when connected to robot WiFi.
Core Plugins
Telemetry Plugin
Text-based telemetry mirroring Driver Hub output.
// Standard FTC telemetry works automatically
telemetry.addData("Position", follower.getPose());
telemetry.addData("State", pathState);
telemetry.update();
Graph Plugin
Visualize data over time - useful for PID tuning and control system validation.
// Add values to graph in loop()
telemetry.addData("Motor Power", motor.getPower());
telemetry.addData("Target Position", targetPos);
telemetry.addData("Current Position", currentPos);
telemetry.update(); // REQUIRED after adding telemetry
Configurables Plugin
Tunable variables that update in real-time.
@Configurable
public class MyOpMode extends OpMode {
// These can be adjusted live from dashboard
public static double kP = 0.1;
public static double kI = 0.0;
public static double kD = 0.01;
public static double targetPosition = 100;
}
Use @Configurable annotation on your OpMode class, then declare public static fields.
Capture Plugin
Records debugging data for offline replay - debug without robot connected.
Dashboard Features
OpMode Control
- Start/stop OpModes from dashboard
- Separate autonomous and teleop sections
- Built-in safety timers
Gamepad Support
- Two FTC gamepad inputs
- Pre-configured button mapping
- Wireless robot control through dashboard
Monitoring
- Battery level tracking
- Network latency/delay monitoring
- Automatic plugin update notifications
Themes & Layout
- Customizable colors
- Resizable widget panels
- Grid-based layout
- Tabbed widget groups
Usage Pattern
@Configurable
@TeleOp(name = "Debug TeleOp")
public class DebugTeleOp extends OpMode {
// Live-tunable from dashboard
public static double driveSpeed = 0.8;
public static double turnSpeed = 0.6;
@Override
public void loop() {
// Telemetry shows in dashboard
telemetry.addData("Drive Speed", driveSpeed);
telemetry.addData("Turn Speed", turnSpeed);
telemetry.addData("Left Stick Y", gamepad1.left_stick_y);
// Use configurable values
double drive = -gamepad1.left_stick_y * driveSpeed;
double turn = gamepad1.right_stick_x * turnSpeed;
telemetry.update();
}
}
What ships with it
1 file 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 · 122 lines · 38 tokens per session scan A 31ab343a5892
panels is a skill published in the GitHub repository ncssm-robotics/ftc-claude (5 stars, last pushed 9mo ago), licensed MIT. It adds 38 tokens to every session and 761 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…