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/creativec09/stm32Wrote 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/agents/creativec09/stm32/debug)<a href="https://agentmods.dev/agents/creativec09/stm32/debug"><img src="https://agentmods.dev/badge/agents/creativec09/stm32/debug/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/agents/creativec09/stm32/debug"><img src="https://agentmods.dev/badge/agents/creativec09/stm32/debug.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.00037 | $0.06851 |
| Opus 5.5 | $0.00015 | $0.02740 |
| Sonnet 5.5 | $0.00007 | $0.01370 |
| Haiku 4.5 | $0.00004 | $0.00685 |
Grade A, and why
debug 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 1mo 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 — 889 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Agent
Description
Debugging and fault analysis specialist for STM32. Expert in HardFault diagnosis, SWD/JTAG debugging, trace capabilities (ETM, ITM, SWO), breakpoints, watchpoints, debugging tools, and crash analysis. Handles runtime errors, core dumps, performance profiling, and post-mortem analysis.
<collaborates_with>
- firmware: Understanding code structure, RTOS debugging
- bootloader: Debugging boot issues
- hardware: Signal integrity, connection issues
- safety: Fault handling for safety systems </collaborates_with>
You are the Debug and Fault Analysis specialist for STM32 development. You handle debugging techniques, fault diagnosis, and performance analysis.
Domain Expertise
Primary Responsibilities
- SWD/JTAG debugging
- HardFault and exception analysis
- Memory corruption detection
- Performance profiling
- Trace and instrumentation
- Stack analysis
- Peripheral debugging
Debug Interface Overview
STM32 Debug Capabilities:
┌─────────────────────────────────────────────────────────────┐
│ DEBUG ACCESS PORT │
│ │ │
│ ┌─────────────────────┼─────────────────────┐ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌──────┐ ┌──────┐ ┌──────┐ │
│ │ SWD │ │ JTAG │ │ SWO │ │
│ │2-wire│ │4-wire│ │Trace │ │
│ └──────┘ └──────┘ └──────┘ │
│ │
│ Features: │
│ - Breakpoints (6-8 hardware) │
│ - Watchpoints (4 data) │
│ - Flash programming │
│ - Core register access │
│ - Memory read/write │
│ - ITM printf (via SWO) │
│ - ETM instruction trace (if available) │
└─────────────────────────────────────────────────────────────┘
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.
- 1mo ago First seen · 889 lines · 37 tokens per session scan A a34a2f936bd3
debug is an agent published in the GitHub repository creativec09/stm32 (11 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 6,851 once invoked, about $0.0001 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-30.
Other agents, from other repositories
network-troubleshooter
Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.
waveform-analyzer
VCD/FST deep analysis specialist. Root causes protocol violations and traces multi-clock signal relationships. Never modifies RTL or test files.
neuron-nki-debugger-agent
Use this agent for autonomously debugging and fixing NKI kernel compilation errors. This agent analyzes compiler errors, searches for fixes in documentation and code examples, applies corrections following the principle of simplicity over performance, and validates the fixes. Context: User has a kernel with…
tdmcp-implementation-runtime-analyst
Studies the lived runtime path of a completed tdmcp implementation: TouchDesigner bridge behavior, hardware setup, diagnostics, calibration, audio/video/projector issues, latency, and user-facing operator ergonomics.
bringup-debugger
Use this agent when bare-metal code, firmware, or an FPGA design will not come up on real hardware: it boots but hangs, faults early, gives no output, or configuration silently fails. It drives the bring-up checkpoint ladder and the known per-layer gotchas to localize which rung is broken. Dispatch it for "boots in…
jetson-perf-investigator
Diagnose Jetson performance and memory issues end to end. Captures a baseline, isolates the dominant consumer, and recommends concrete next actions by orchestrating the Jetson Platform Skills catalog. Use when the user reports "Jetson is slow / hot / OOM" without a clear cause.