Borrowing it
Nothing to install: this file belongs to odere-pro/claude-aws-architect. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/odere-pro/claude-aws-architect/main/CLAUDE.mdgit 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/instructions/odere-pro/claude-aws-architect/claude-md)<a href="https://agentmods.dev/instructions/odere-pro/claude-aws-architect/claude-md"><img src="https://agentmods.dev/badge/instructions/odere-pro/claude-aws-architect/claude-md.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.01160 | $0.01160 |
| Opus 5 | $0.00580 | $0.00580 |
| Sonnet 5 | $0.00232 | $0.00232 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
claude-aws-architect CLAUDE.md 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 8d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — entry-point notes for claude-aws-architect
This file is loaded into every Claude Code session opened from the
plugin's own repository. It exists to satisfy SPEC-v4 §H2 — the
plugin's repo points back at its own /aws command and its own
spec — so the plugin can be developed, dogfooded, and tested
inside Claude Code without external scaffolding.
Plugin entry point
- Run
/awsin any Claude Code session to invoke the Well-Architected SDLC orchestrator. The command lives atcommands/aws.mdand routes by the §5.6 depth-classification rules in SPEC.md and docs/plan/SPEC-v4.md. - Run
/aws-spec <feature>to validate an existing spec under.claude/specs/<feature>/against §11.A and §11.B gates. - Run
/aws-doctorto verify the host has the required CLIs (uvx,jq,aws) and that every MCP server in.mcp.jsonresolves.
Self-dogfood
- The plugin's own meta-spec lives under
.claude/specs/claude-aws-architect/per SPEC-v4 §H1; that directory is the release-dogfood acceptance artefact for the v0.1.0 tag (§11.E gate 34, §13.G). - The canonical executable example lives under
templates/examples/order-processing-pipeline/per §H5; that directory is the read-only reference §11 gates point at for any consumer asking what a populated spec looks like. - The
aws-secret-scannerandaws-api-write-guardPreToolUse hooks default-on; both are wired inhooks/hooks.jsonand apply inside this repo as well as in any consumer project.
Where the spec lives
- SPEC.md — the canonical plugin spec, kept short.
- docs/plan/SPEC-v4.md — the full v4 declarative spec; sections 0–18.
- docs/plan/PR-PLAN.md — the 33-PR execution roadmap with dependencies and parallel-safe flags.
- docs/plan/PR-CONVENTIONS.md — branch naming, commit format, merge strategy.
- docs/adr/ — architectural decision records A1–A7.
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.
- 8d ago First seen · 92 lines · 1,160 tokens per session scan A e4d5aba91120
claude-aws-architect CLAUDE.md is an instructions file published in the GitHub repository odere-pro/claude-aws-architect (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,160 tokens to every session, about $0.0058 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.