What is arm-cortex-expert?

A specialist for software running on ARM Cortex-M microcontrollers, which are small chips used in embedded devices. It focuses on firmware and hardware-driver code for platforms such as STM32, Teensy, nRF52, and SAMD.

Use it to create or review drivers for I²C, SPI, UART, ADC, DAC, PWM, and USB, and to improve interrupt handling, DMA, scheduling, and memory use.

It helps address hardware timing, interrupts, memory, data transfers, and device communication issues that are easy to get wrong in embedded software.

arm-cortex-expert — Agent for Claude Code by calinfaja/K-LEAN

Install

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.

Clone the repo

git clone --depth 1 https://github.com/calinfaja/K-LEAN

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/calinfaja/k-lean/arm-cortex-expert/github.svg)](https://agentmods.dev/agents/calinfaja/k-lean/arm-cortex-expert)

Your own site

<a href="https://agentmods.dev/agents/calinfaja/k-lean/arm-cortex-expert"><img src="https://agentmods.dev/badge/agents/calinfaja/k-lean/arm-cortex-expert/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/calinfaja/k-lean/arm-cortex-expert"><img src="https://agentmods.dev/badge/agents/calinfaja/k-lean/arm-cortex-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 93 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,697 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 91% copy Near-identical to another mod in the catalogue.

Token cost

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.00093	$0.03697
Opus 5.5	$0.00037	$0.01479
Sonnet 5.5	$0.00019	$0.00739
Haiku 4.5	$0.00009	$0.00370

Measured 1mo ago against content hash 61e2b7efa3d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

arm-cortex-expert 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.

Origin

This is a copy

91% identical to arm-cortex-expert — 143 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

src/klean/data/agents/arm-cortex-expert.md · 338 lines

How it starts

The opening of the file, as written. The whole thing — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Citation Requirements

All findings MUST include verified file:line references:

Use grep_with_context to find issues - it returns exact line numbers
ONLY cite line numbers that appear in tool output
Include code snippet context for each finding
Format: driver.c:123 or src/peripheral.c:45-50