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/creativec09/stm32/stm32-setupgit clone --depth 1 https://github.com/creativec09/stm32What 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.00020 | $0.03779 |
| Opus 5 | $0.00010 | $0.01889 |
| Sonnet 5 | $0.00004 | $0.00756 |
| Haiku 4.5 | $0.00002 | $0.00378 |
Grade C, and why
stm32-setup scanned grade C with 2 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 2d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -LsSf https://astral.sh/uv/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -LsSf https://astral.sh/uv/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STM32 MCP Setup Command
Interactive setup for the STM32 documentation server. Handles dependency installation and project configuration.
Usage
/stm32-setup Full setup (install deps, check MCP, update CLAUDE.md)
/stm32-setup --status Show current installation status
/stm32-setup --update-claude Only update project CLAUDE.md
/stm32-setup --force-db Force re-download of database
Instructions for the Assistant
When the user runs /stm32-setup, follow these steps IN ORDER:
Step 0: Detect Existing Agent Installations (CRITICAL - DO THIS FIRST)
IMPORTANT: Before installing anything, you MUST check for existing agent installations in BOTH locations to avoid duplicate installs.
Directory Definitions:
- LOCAL =
./.claude/agents/(project directory, relative to cwd) - GLOBAL =
~/.claude/agents/(user's home directory)
Detection Steps:
-
Check LOCAL installation first:
ls -la ./.claude/agents/*.md 2>/dev/null | head -5 -
Check GLOBAL installation:
ls -la ~/.claude/agents/*.md 2>/dev/null | head -5 -
Look for STM32-specific agents (router.md, firmware.md, debug.md, etc.):
ls ./.claude/agents/router.md ~/.claude/agents/router.md 2>/dev/null
Decision Matrix:
| Local Exists? | Global Exists? | Action |
|---|---|---|
| YES | (any) | Report "Agents installed locally" → Skip to Step 2 (MCP check) |
| NO | YES | Report "Agents installed globally" → Ask if user wants local copy too |
| NO | NO | Proceed with installation (Step 1) |
Priority Rule: Local installation takes precedence. If agents exist locally, DO NOT install globally. This prevents cross-project contamination.
Example Output:
Checking for existing STM32 agent installations...
Local (./.claude/agents/): 16 agents found ✓
Global (~/.claude/agents/): 0 agents found
Status: Agents already installed locally. Skipping installation.
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.
- 2d ago First seen · 447 lines · 20 tokens per session scan C ebc772643553
stm32-setup is a command published in the GitHub repository creativec09/stm32 (11 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 3,779 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.