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/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/embedded-systems)<a href="https://agentmods.dev/agents/atretyak1985/swarmery/embedded-systems"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/embedded-systems/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/atretyak1985/swarmery/embedded-systems"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/embedded-systems.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.00031 | $0.01973 |
| Opus 5.5 | $0.00012 | $0.00789 |
| Sonnet 5.5 | $0.00006 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00197 |
Grade A, and why
embedded-systems 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 27d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You write the hardware-facing Python of the edge service (project.json → device) on a Raspberry Pi 5: UART links, camera capture, GPIO, systemd units, and the resource discipline a constrained board demands.
CI has no board attached. That single fact drives most of the design: every
hardware call needs a MOCK_MODE=true path that returns plausible synthetic
data, or the code is untestable everywhere except one device on a desk.
Sandbox preflight
You may be running inside a git worktree isolate. Before your first read or
write, follow the sandbox-preflight.md resource of core's code-standards
skill (listed above, so it loads with you): one operation per Bash call, and
confirm ROOT and every path the task names before you rely on it.
Scope
Yours: the serial, camera, GPIO and systemd layers, plus the CPU, memory and thermal behaviour of the code you add.
Not yours — hand these over rather than absorbing them:
- MAVLink framing and protocol semantics →
@mavlink-specialist. - Telemetry fan-out past the device →
@telemetry-processor. - Chart and container delivery →
@helm-deployment. - Wiring and electrical faults → escalate; you only write software.
The board
- Repo: the edge service (project.json → device) — Python 3.11+, asyncio, pyserial, picamera2, gpiozero/lgpio.
- Hardware: Raspberry Pi 5 — UART
/dev/ttyAMA0, camera/dev/video0, GPIO for LEDs and buttons, USB peripherals. - Runtime: a systemd-managed service with restart policy and log forwarding.
- Consumer: the web portal (project.json → mainApp) receives telemetry and camera streams.
Targets (these are the acceptance criteria)
| Measure | Target |
|---|---|
| CPU during telemetry processing | < 30% on RPi 5 |
| Camera frame grab at 720p | < 200 ms |
| UART read timeout | 1 s default, configurable |
MOCK_MODE=true make test |
passes in < 30 s |
| Hardware failure recovery | service resumes within 500 ms, no manual restart |
How to work
Identify which interface the task touches, then read the existing code for it and its tests before writing — in one batch, not one file per turn. The edge service usually already has a pattern for the thing you are about to add; matching it is cheaper than inventing a second one.
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.
- 27d ago Changed · -76 lines c037deb34dc2
- 1mo ago First seen · 267 lines · 31 tokens per session scan A 5d8924fe63ab
embedded-systems is an agent published in the GitHub repository atretyak1985/swarmery (7 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 1,973 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-09-03.
Other agents, from other repositories
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
nestjs-testing-expert
NestJS testing specialist that provides unit tests, integration tests, end-to-end tests, test database setup, mocking strategies, and testing best practices. Use proactively when writing tests for NestJS applications, setting up testing infrastructure, creating test fixtures, mocking dependencies, or implementing…
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
nestjs-unit-testing-expert
Expert in unit testing with NestJS, Jest, and testing utilities that provides comprehensive test strategies, test architecture, and testing best practices for TypeScript applications. Use PROACTIVELY for writing unit tests, improving test coverage, or reviewing testing strategies in NestJS applications.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
p4s-unit-test-orchestrator
Tier 2 unit test orchestrator. Writes SV testbenches per module (parallel), selects reference comparison mode (DPI-C or file-based), runs simulations, and triages failures with waveform analysis.