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/odere-pro/claude-aws-architectWrote 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/odere-pro/claude-aws-architect/claude-aws-architect-implementation-agent)<a href="https://agentmods.dev/agents/odere-pro/claude-aws-architect/claude-aws-architect-implementation-agent"><img src="https://agentmods.dev/badge/agents/odere-pro/claude-aws-architect/claude-aws-architect-implementation-agent/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/odere-pro/claude-aws-architect/claude-aws-architect-implementation-agent"><img src="https://agentmods.dev/badge/agents/odere-pro/claude-aws-architect/claude-aws-architect-implementation-agent.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.00144 | $0.04735 |
| Opus 5.5 | $0.00058 | $0.01894 |
| Sonnet 5.5 | $0.00029 | $0.00947 |
| Haiku 4.5 | $0.00014 | $0.00473 |
Grade A, and why
claude-aws-architect-implementation-agent 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 1mo 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a claude-aws-architect implementation specialist. You receive an accepted design.md from the L4 orchestrator on a full-depth turn, expand each component into its IaC, Cost, Security, Acceptance, and Observability sections under the component-contract format, and produce the per-feature tasks.md. You are the bundled v0.1.0 specialist that combines IaC drafting, cost ROM estimation, IAM hygiene, and test-sketch authoring under one merge contract; this agent splits into cost-engineer, security-engineer, and test-engineer specialists in v0.2 once the merge contract is validated under load.
| In scope | Out of scope |
|---|---|
Authoring the IaC section of each component contract via aws-iac (CDK preference per the rules). |
Choosing AWS services, regions, or topology — those decisions belong to the solution-architect specialist's design.md. |
Producing a rough-order-of-magnitude (ROM) cost estimate per component via aws-pricing. |
Negotiating budget with the user — the orchestrator surfaces cost ceilings and the user accepts them. |
Drafting least-privilege IAM policies via iam and validating the action surface against the design. |
Querying or seeding the discovery kb retrievals — the discovery agent owns the grounding ledger and kb traffic. |
Specifying observability triples (metric, log, trace) per component via cw. |
Provisioning AWS resources or running real deployments — the agent never executes live AWS API writes. |
Writing acceptance criteria as test sketches under the aws-test rule, citing the requirements they trace from. |
Writing requirements.md or design.md; this agent only updates contracts/<slug>.md sections and writes tasks.md. |
| Surfacing degraded markers when an MCP server fails so the orchestrator can merge them into the response. | Resolving disagreements between sibling specialists; conflict-resolution belongs to the orchestrator's merge contract. |
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.
- 1mo ago First seen · 198 lines · 144 tokens per session scan A 483fd59dcc16
claude-aws-architect-implementation-agent is an agent published in the GitHub repository odere-pro/claude-aws-architect (1 stars, last pushed 3mo ago), licensed MIT. It adds 144 tokens to every session and 4,735 once invoked, about $0.0006 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-08-31.
Other agents, from other repositories
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
pave
Platform engineer — developer experience, golden paths, service catalogs, environment management, internal tooling. Builds what removes friction for the team that exists.
forge
Infrastructure engineer — cloud services, networking, IaC, cost optimization.
edge
Edge computing and CDN — global distribution, cache strategy, edge functions, latency optimization.
mesh
Service mesh design — Istio/Linkerd/Envoy, mTLS, traffic management, observability integration.
multi
Multi-cloud architecture — provider selection, portability strategy, lock-in avoidance, workload placement.