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 skills add odere-pro/claude-aws-architect --skill aws-component-contractgit 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/skills/odere-pro/claude-aws-architect/aws-component-contract)<a href="https://agentmods.dev/skills/odere-pro/claude-aws-architect/aws-component-contract"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-aws-architect/aws-component-contract/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/skills/odere-pro/claude-aws-architect/aws-component-contract"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-aws-architect/aws-component-contract.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.00061 | $0.01695 |
| Opus 5 | $0.00030 | $0.00847 |
| Sonnet 5 | $0.00012 | $0.00339 |
| Haiku 4.5 | $0.00006 | $0.00169 |
Grade A, and why
aws-component-contract 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Apply this skill any time an agent writes, edits, or reviews a component contract — the per-component design artefact that ships with every generated AWS component. The solution-architect agent emits these at design time; the implementation agent fills in the IaC, cost, security, and observability sections; reviewers lint them before status transitions to accepted or implemented.
Trigger conditions:
- The agent is creating a new file under
.claude/specs/<feature>/contracts/<slug>.md. - The agent is editing an existing contract and needs to confirm the section order is preserved.
- The agent is filling in the
talks-toarray and needs to verify the named slugs resolve to sibling contracts in the same feature. - The agent is filling in the Observability section and needs to confirm the metric/log/trace triple is complete.
- The agent is performing a pre-acceptance review and needs to lint every contract under the feature.
Procedure
- Place the file at the canonical path.
.claude/specs/<feature>/contracts/<component-slug>.md. The component slug is lowercase-kebab-case, ≤50 chars, matches^[a-z][a-z0-9-]*[a-z0-9]$. If creating, useassets/contract.md.tmplas the starting structure. - Populate the frontmatter. Required keys per
references/contract-schema.md:component,kind,version,status,talks-to(array, may be empty if no siblings),grounded-by(array, ≥1 entries in<server>:<short-key>format). - Maintain section order. The body has seven sections in this exact order: Purpose, Interface, Sequence, Component view (C4 L3), Acceptance criteria, Observability, Integration points. No reorder, no merge, no rename.
- Resolve
talks-tointegration links. Every slug intalks-tomust reference an existing contract file under the same feature'scontracts/directory. Dangling references are a lint failure. - Complete the observability triple. The Observability section requires three subsections — Metric, Log, Trace — each populated with at least one concrete signal name and source. Empty triples are a lint failure; "TBD" is not a valid signal. Detail in
references/observability-triple.md. - Cite the grounding. The
grounded-byarray must contain at least one valid<server>:<short-key>citation pointing to a ledger entry that justifies the component's choice of service, quota assumption, or pricing assumption.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 65 lines · 61 tokens per session scan A e8943e5be878
aws-component-contract is a skill published in the GitHub repository odere-pro/claude-aws-architect (1 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,695 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-31.
Other skills, from other repositories
deployment
Hosting, deployment, CI/CD, and going live. Activated when Claude works with deployment configs, Dockerfiles, Vercel/Netlify configs, or deployment-related commands.
ec2
AWS EC2 virtual machine management — instances, security groups, key pairs, AMIs, EBS volumes, Auto Scaling Groups, Spot Instances, Session Manager, placement groups, and instance lifecycle automation. Trigger on ANY of these, even when EC2 isn't named explicitly: - Launching or provisioning: "spin up a server"…
cloudwatch
AWS CloudWatch monitoring for logs, metrics, alarms, and dashboards. Use when setting up monitoring, creating alarms, querying logs with Insights, configuring metric filters, building dashboards, or troubleshooting application issues.
ecs
AWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.
cloudformation
AWS CloudFormation infrastructure as code for stack management. Use when writing templates, deploying stacks, managing drift, troubleshooting deployments, or organizing infrastructure with nested stacks.
eks
AWS EKS Kubernetes management for clusters, node groups, and workloads. Use when creating clusters, configuring IRSA, managing node groups, deploying applications, or integrating with AWS services.