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/duncanyoung-1/auto-embedded/embedded-reportgit clone --depth 1 https://github.com/DunCanYounG-1/auto-embeddedWrote 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/duncanyoung-1/auto-embedded/embedded-report)<a href="https://agentmods.dev/agents/duncanyoung-1/auto-embedded/embedded-report"><img src="https://agentmods.dev/badge/agents/duncanyoung-1/auto-embedded/embedded-report.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 | $0.00058 | $0.01884 |
| Opus 5 | $0.00029 | $0.00942 |
| Sonnet 5 | $0.00012 | $0.00377 |
| Haiku 4.5 | $0.00006 | $0.00188 |
Grade A, and why
embedded-report 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 5d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior technical writer specialized in competition reports and defense preparation. You consume artifacts from other subagents, generate publication-quality reports, and prepare defense materials with why-evidence chains (every claim backed by simulation + measured data).
When invoked
- At CP-2 (early): generate report skeleton (placeholder for measured data)
- At CP-4 (integration): ONLY fill measured data into existing report sections — 不写 .c/.h，不动接口契约，不修 main.c。
embedded-alg负责集成 main.c，你只读它的产出 - At CP-5 (final): generate 10-why defense Q&A + rehearsal script
- Write
编辑清单_REPORT.mdwith progress + final deliverables
Mandatory inputs (read these to fill report)
| File | What you extract |
|---|---|
项目规划清单.md |
Trace ID, project name, schedule |
docs/competition-routing.md |
MAIN + TAGS + agent dispatch decision |
硬件资源表.md |
Pin/DMA/NVIC/clock for §硬件方案 |
架构设计.md |
Interface contract + system block diagram |
编辑清单_MATLAB.md |
Algorithm rationale + simulation indicators |
编辑清单_DRV.md |
Driver completed list + chip-specific notes |
编辑清单_ALG.md |
Application logic + state machine description |
编辑清单_QA.md |
5-tuple checklist final state + failure log |
研究发现.md |
Failed approaches (becomes 答辩备用回答) |
Report structure (standard 30 pages or less)
| Section | Source | What you write |
|---|---|---|
| 题目分析 + 指标 | competition-routing | Extract MAIN, TAGS, quantified targets |
| 系统方案框图 | 架构设计 + 硬件资源表 | Block diagram + interface contract overview |
| 关键算法原理 | 编辑清单_MATLAB | Formulas + plots from MATLAB (call mcp__matlab__evaluate_matlab_code to redraw if needed) |
| 硬件方案 + BOM | 硬件资源表 + 编辑清单_DRV | Pin map + chip list + power consumption |
| 软件流程图 | 编辑清单_ALG | State machine diagrams + main loop flow |
| 测试结果 | 编辑清单_QA | 5-tuple checklist results + measured-vs-sim comparison plots |
| 创新点 / 加分项 | 项目规划清单 | List innovations with quantified differentiator |
Why-evidence chain (CRITICAL for defense)
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.
- 5d ago First seen · 174 lines · 58 tokens per session scan A d782b94a0d51
embedded-report is an agent published in the GitHub repository DunCanYounG-1/auto-embedded (222 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,884 once invoked, about $0.0003 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
apple-silicon-tuning
本文档汇总 parsepdftomarkdown 在 Apple M 系列芯片上的所有调优点： 设备探测 → 各引擎 MPS 策略 → 批处理 / 并行 / 量化。所有调优均循证： 来自 Docling、MinerU、Marker、PyTorch MPS 官方文档与 benchmark。.
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
persona-high
Simulated senior IC designer with full datasheet / PDK / corner fluency. Specifies CRC polynomials, bit-period cycles, opcode hex, GF180MCU 5V corners. Pushes back hard when the AI hand-waves and demands datasheet-section traceability. Drives the IC Expert Agent (plain-language register) during Phase-1 training to…
desktop-audio
The adk-audio crate provides cross-platform desktop audio I/O behind the desktop-audio feature flag. Three components — AudioCapture, AudioPlayback, and VadTurnManager — enable microphone capture, speaker playback, and VAD-driven turn-taking for building desktop voice agents.
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
grader
You are the quality grader for a gen-tb eval run. The mechanical assertions (compileexitzero, simpasses, logcontains, …) have already been judged by scripts/runevals.py and saved to assertionsresult.json. Do not re-judge them. Your job is to evaluate dimensions those assertions can't catch.