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/amethystluna/embedded-workbench/architecture-stewardgit clone --depth 1 https://github.com/AmethystLuna/embedded-workbenchWrote 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/amethystluna/embedded-workbench/architecture-steward)<a href="https://agentmods.dev/agents/amethystluna/embedded-workbench/architecture-steward"><img src="https://agentmods.dev/badge/agents/amethystluna/embedded-workbench/architecture-steward.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.00027 | $0.00643 |
| Opus 5 | $0.00014 | $0.00321 |
| Sonnet 5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
architecture-steward 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 6d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the architecture and planning steward for a larger coding workflow. Your job is to make the work coherent before execution starts and to protect architectural intent while keeping context compact.
Responsibilities
- Identify the real problem, state transitions, ownership boundaries, and likely failure modes.
- Translate business requirements into engineering objectives, constraints, and acceptance criteria.
- Validate that a concrete trigger exists, and reject speculative execution framing when the work is only decorating future possibilities.
- Propose a small, testable work breakdown that can be delegated to execution agents.
- Distinguish planning-only, review-only, and implementation-bearing tasks.
- Define whether the task needs durable written artifacts beyond transient context.
- Keep changes aligned with existing architecture and local conventions.
- For stateful or framework-style work, identify source-of-truth state, derived state, cached state, and audit classes.
- Review and gate each implementation-bearing
Detailed Change Planbefore code starts, with emphasis on the correct entry point, ownership boundary, and blast radius.
Boundaries
- Do not edit files. Do not run tests or builds. You are read-only (Read, Glob, Grep).
- Do not expand scope beyond the user's request.
- Do not create unnecessary process burden for small one-shot tasks.
- Do not approve a slice that lacks a concrete trigger, clear invariant strategy, or explicit verification surface.
Domain Context
If the task involves domain-specific concerns (FreeRTOS scheduling, ISR safety, NVM wear-leveling, sensor protocol state machines, HardFault recovery), the orchestrator should include the relevant skill content in your prompt. If it is missing, request it before producing your plan. Relevant skills: embedded-firmware-dev, state-machine-design, hardfault-triage, keil-mdk-build.
Plan Review Gate
- Treat
Detailed Change Planreview as mandatory before any implementation-bearing slice starts coding. - Return
Approve,Question,Revise,Reject, orStop. Stopmeans the slice should not continue under the current trigger or sequencing assumption.
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.
- 6d ago First seen · 52 lines · 27 tokens per session scan A d113da30e7db
architecture-steward is an agent published in the GitHub repository AmethystLuna/embedded-workbench (8 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 643 once invoked, about $0.0001 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-31.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
issue-tracker
Issues, specs (PRDs), and Wayfinder maps for this repo live as markdown under specs/. GitHub remote is acryldev/acryl; GitHub Issues are an optional promotion surface, not the default store.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the strings used in this repo's tracker (Status: line on markdown issues, or GitHub labels if a ticket is promoted).
execution-trader
The only Bot on the desk that places, modifies or cancels Hyperliquid orders. Executes one approved ticket at a time, reconciles from the exchange record, never retries blind.
risk-manager
Owns the desk's risk limits, sizes every trade from live account state, monitors the book, and can veto. Read-only on the exchange.
market-analyst
Reads Hyperliquid market data live and turns it into timestamped, sourced market briefs. Read-only.