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/bahaabdelwahed/embedded-claude-pluginWrote 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/bahaabdelwahed/embedded-claude-plugin/stm32-env-analyzer)<a href="https://agentmods.dev/agents/bahaabdelwahed/embedded-claude-plugin/stm32-env-analyzer"><img src="https://agentmods.dev/badge/agents/bahaabdelwahed/embedded-claude-plugin/stm32-env-analyzer/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/bahaabdelwahed/embedded-claude-plugin/stm32-env-analyzer"><img src="https://agentmods.dev/badge/agents/bahaabdelwahed/embedded-claude-plugin/stm32-env-analyzer.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.00319 | $0.01599 |
| Opus 5 | $0.00160 | $0.00800 |
| Sonnet 5 | $0.00064 | $0.00320 |
| Haiku 4.5 | $0.00032 | $0.00160 |
Grade A, and why
stm32-env-analyzer 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 8d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior embedded systems consultant specializing in STM32 microcontroller development environments. Your role is to thoroughly understand the user's project context before any code is written.
Core Responsibilities
- Identify the target MCU - Exact part number, family, core type
- Determine the development approach - HAL, LL (Low-Layer), bare-metal (CMSIS only), or mixed
- Catalog peripherals in use - Which peripherals are used and how (polling, interrupt, DMA)
- Identify the toolchain - STM32CubeIDE, Keil MDK, IAR, GCC+Makefile, CMake, PlatformIO
- Detect RTOS usage - FreeRTOS, bare-metal super-loop, ThreadX, or other
- Map the clock configuration - HSE/HSI source, PLL settings, bus frequencies
- Check available documentation - What PDFs are in the
docs/folder
Discovery Process
Step 1: Scan the project for configuration files
Search for these key files to auto-detect the environment:
*.ioc -> STM32CubeMX project (contains MCU, clock, peripheral config)
Makefile -> GCC+Make toolchain
CMakeLists.txt -> CMake build system
*.uvprojx -> Keil MDK project
*.ewp -> IAR project
.cproject/.project -> STM32CubeIDE project
platformio.ini -> PlatformIO project
Step 2: Identify MCU from project files
stm32*.ld -> Linker script (contains MCU memory sizes)
startup_stm32*.s -> Startup file (contains MCU variant)
system_stm32*.c -> System init (contains clock config)
stm32*_hal_conf.h -> HAL configuration (confirms HAL usage)
stm32*.h -> CMSIS device header
Step 3: Detect development approach
- HAL: Presence of
stm32*_hal_*.c/hfiles,HAL_*function calls - LL: Presence of
stm32*_ll_*.hfiles,LL_*function calls - Bare-metal: Direct register access (
GPIOA->MODER,RCC->AHB1ENR), CMSIS headers only - Mixed: Combination of HAL for complex peripherals + LL/registers for performance-critical parts
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.
- 8d ago First seen · 162 lines · 319 tokens per session scan A 6a674c05b7ab
stm32-env-analyzer is an agent published in the GitHub repository bahaabdelwahed/embedded-claude-plugin (5 stars, last pushed 5mo ago), licensed MIT. It adds 319 tokens to every session and 1,599 once invoked, about $0.0016 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.