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 commands/odere-pro/claude-aws-architect/awsgit 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/commands/odere-pro/claude-aws-architect/aws)<a href="https://agentmods.dev/commands/odere-pro/claude-aws-architect/aws"><img src="https://agentmods.dev/badge/commands/odere-pro/claude-aws-architect/aws.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.00036 | $0.00654 |
| Opus 5 | $0.00018 | $0.00327 |
| Sonnet 5 | $0.00007 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
aws 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are invoking the claude-aws-architect orchestrator for an AWS architecture, design, IaC, threat-model, cost-estimate, or runbook prompt.
Inputs
- User prompt:
$ARGUMENTS - Per-feature directory (if continuing an existing feature):
.claude/specs/<feature>/ - MCP servers configured by
.mcp.jsonat the plugin root:aws-knowledge,aws-iac,aws-pricing,well-architected-security,iam,cloudwatch.
Action
Delegate to the claude-aws-architect-orchestrator-agent subagent. The subagent owns:
- Depth classification (shallow direct-answer vs full parallel fan-out) per the depth heuristic in
aws-sdlc-workflow. - On full depth: a single message containing parallel
Agentinvocations of the eligible L3 specialists (claude-aws-architect-discovery-agent,claude-aws-architect-solution-architect-agent,claude-aws-architect-implementation-agent) followed by a merged response per the merge contract. - On shallow depth: a citation-backed direct answer; no artefacts written.
- Surfacing every degraded marker under
## Degraded signalsand every unresolved disagreement under## Open Questions. - Final-assembly writes of
.claude/specs/<feature>/{requirements,design,tasks}.mdonly when the corresponding specialist returned content this turn.
Boundaries
- This command does not bypass the orchestrator: never call MCP servers or sibling specialists directly from the command body.
- This command does not invent a feature slug. If the prompt does not name an existing feature, the orchestrator allocates a fresh slug and creates
.claude/specs/<slug>/on first artefact write. - This command does not write artefacts on a shallow turn.
- For purely read-only knowledge lookups ("what is X", CLI reference, comparisons, onboarding pointers, "what should I learn next"), prefer
/aws-kb— it routes to the kb-navigator with a tighter response template and no spec-artefact writes. The orchestrator may suggest/aws-kbonce when a shallow prompt has no SDLC-artefact intent.
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 · 51 lines · 36 tokens per session scan A cb592c28a74d
aws is a command published in the GitHub repository odere-pro/claude-aws-architect (1 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 654 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-08-31.
Other commands, from other repositories
progress
View your CodeSensei learning dashboard — belt rank, XP, streaks, and skills.
recap
Get a summary of everything you learned this session — concepts, quizzes, and progress.
caiq-generate
Generate CAIQ (Consensus Assessments Initiative Questionnaire) responses.
map-framework
Map CSA CCM controls to other compliance frameworks.
AWS Inspector Collect
Query AWS for compliance-relevant configuration across IAM, S3, CloudTrail, EBS, and emit findings conforming to the v1 contract.
oma:modernize
브라운필드 레거시 워크로드를 AWS 로 현대화하는 6단계 루프 입구. workload-assessment → modernization-strategy → to-be-architecture → containerization → cutover-planning 을 modernization-architect 가 오케스트레이션하며, 각 phase 경계에서 risk-discovery 와 audit-trail 을 자동 호출합니다.