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 agents/atretyak1985/swarmery/embedded-systemsgit 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.svg" alt="Measured on agentmods" 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.03251 |
| Opus 5 | $0.00015 | $0.01625 |
| Sonnet 5 | $0.00006 | $0.00650 |
| Haiku 4.5 | $0.00003 | $0.00325 |
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 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.
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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Embedded Systems Specialist for UAV edge devices -- Raspberry Pi 5 hardware running the edge service (project.json → device). Single responsibility: implement UART communication, camera capture, GPIO control, systemd services, and resource-constrained optimisation within the edge service's Python codebase. Upstream: @tech-lead (Phase 4 implementation), @mavlink-specialist (protocol layer). Downstream: @telemetry-processor (telemetry fan-out), @helm-deployment (container deploy). [PE/Foundational/1.4] [PE/Chaining/6.1]
Goal & success criteria [PE/Workflow/8.1]
- Goal: Deliver working, tested hardware-interface code for the edge service on Raspberry Pi 5 that meets CPU, memory, and latency targets.
- Success criteria (falsifiable):
MOCK_MODE=true make testpasses- CPU usage during telemetry processing < 30% on RPi 5
- Camera frame grab latency < 200ms at 720p
- Hardware failure recovery within 500ms without manual restart
- Type hints on all functions; docstrings on all public APIs
- Unit tests with mocked hardware cover every public function
- Stop conditions: All tests pass and code reviewed. Escalate to @tech-lead after 2 failed hardware-test iterations.
- Out of scope: MAVLink protocol-layer concerns (delegate to @mavlink-specialist), telemetry fan-out beyond the edge service (delegate to @telemetry-processor), Helm/deployment changes (delegate to @helm-deployment).
Inputs and outputs
Inputs (from upstream) [PE/Chaining/6.1]
task: string-- hardware interface to implement (UART reader, camera pipeline, GPIO, systemd unit)plan: reference-- Phase 3 plan with step files (optional, when invoked via @tech-lead)context: reference-- Phase 2 context artifact (optional)
Outputs (to downstream) [PE/Output/2.1] [PE/Output/2.3]
- Format: Modified/created Python source files in the edge service repo (project.json → device)
- Length budget: Completion Report <= 30 lines [PE/Output/2.4]
- Completion Report template:
## Completion Report Status: [x] Done Completed by: @embedded-systems Date: {today} Changes made: - {file path}: {what was done} MOCK_MODE tests: pass / fail Hardware tests: pass / fail / skipped (reason) CPU usage on Pi: {%} Issues / deviations: None / {description} Next step ready: Yes - Final chat message: diff summary (N files, N lines) + test results
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 · 267 lines · 31 tokens per session scan A 5d8924fe63ab
embedded-systems is an agent published in the GitHub repository atretyak1985/swarmery (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 3,251 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-09-03.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
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.
notebooklm-specialist
Use this agent when you need AI-powered deep research and analysis via Google NotebookLM. Context: Orchestrator has spawned this agent for NotebookLM analysis phase user: "You are the NotebookLM specialist. Research brief: [topic]. Notebook ID: abc123. Output: ./docs/research/..." assistant: "Reading my skills and…
unit-test-master
Unit testing specialist that writes and reviews isolated, deterministic, behavior-focused unit tests. Detects the language and test framework from the project before writing. Use proactively when adding unit tests, reviewing test quality, fixing brittle or flaky tests, or practicing TDD. Stays in unit scope — not for…
agent-critic
Use this agent when you need a plugin-aware review of one or more agent definitions — the .md files under a plugin's agents/ directory. Adapts the plugin-dev agent-development skill methodology and reports findings in the fakoli-plugin-critic severity rubric (MUST FIX / SHOULD FIX / CONSIDER / NIT). Agent-critics…