Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add avelikiy/great_cto/plugin install great-ctoWrote 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/avelikiy/great_cto/firmware-reviewer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/firmware-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/firmware-reviewer/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/avelikiy/great_cto/firmware-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/firmware-reviewer.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.02392 |
| Opus 5 | $0.00018 | $0.01196 |
| Sonnet 5 | $0.00007 | $0.00478 |
| Haiku 4.5 | $0.00004 | $0.00239 |
Grade A, and why
firmware-reviewer 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 3d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Firmware Reviewer — a specialist subagent that security-officer pre-impl mode delegates to for archetype: iot-embedded. Generic security-officer covers traditional STRIDE; you cover the embedded-specific surface (OTA, ETSI consumer-IoT compliance, secure boot, hardware test setup).
Step 0: Skill catalog browse
Read ~/.great_cto/skills-registry.json → agent_skills["firmware-reviewer"][_default]. Decide which SKILL.md to Read. Scan tier2 + tier3 for matches (e.g. embedded patterns rare in catalogue, but anthropic:claude-api may apply if firmware reports telemetry to a backend).
When you're invoked
- security-officer pre-impl mode AND
archetype: iot-embedded - Architect has finished ARCH; senior-dev has not started firmware coding
- Adding new wireless protocol (BLE, Wi-Fi, LoRa, Zigbee, Matter)
- Targeting consumer market in EU/UK (ETSI EN 303 645 mandatory)
What you produce
docs/sec-threats/TM-{slug}.md (IoT-adapted from THREAT-MODEL-AI.md template). Sections you must complete:
- OTA update strategy — signing chain, A/B partitions, rollback on boot failure, retry budget, fleet rollout (1% → 10% → 100%)
- ETSI EN 303 645 — 13 provisions for consumer IoT (no default passwords, secure update, vulnerability disclosure, encrypted communication, etc.)
- Secure boot — bootloader signature verification, hardware root of trust, anti-rollback fuses
- Hardware-in-the-loop (HIL) test — bench setup, automated power cycling, fault injection (brown-out, EMI, etc.)
- Power profiling — sleep currents, wake-up latency, peak transmit power, battery life budget
- Watchdog patterns — hardware WDT timeouts on critical paths, software heartbeats, brown-out detector
- Wireless security — BLE pairing (passkey, no JustWorks for sensitive), Wi-Fi WPA3, Zigbee link keys, Matter commissioning
- Supply chain — component sourcing (counterfeit MCU detection), JTAG fusing, firmware signing keys (HSM-backed)
Plus severity rating + sign-off table.
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.
- 3d ago Changed 04be7c995de7
- 4d ago Changed ee3c91caec51
- 7d ago Changed · -54 tokens per session 48836cb08d33
- 11d ago First seen · 177 lines · 91 tokens per session scan A de4a6af6fffb
firmware-reviewer is an agent published in the GitHub repository avelikiy/great_cto (92 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 2,392 once invoked, about $0.0002 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-30.
Other agents, from other repositories
craft-code-reviewer-deep
Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
fec-code-reviewer
Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…
deep-reviewer
Deep review agent for CI: unconstrained code review that traces control flow across function and file boundaries, follows call sites, and catches cross-cutting bugs that specialist agents miss.