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-waf-performance-efficiency-skillgit 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-waf-performance-efficiency-skill)<a href="https://agentmods.dev/skills/odere-pro/claude-aws-architect/aws-waf-performance-efficiency-skill"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-aws-architect/aws-waf-performance-efficiency-skill/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-waf-performance-efficiency-skill"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-aws-architect/aws-waf-performance-efficiency-skill.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.00071 | $0.01352 |
| Opus 5 | $0.00036 | $0.00676 |
| Sonnet 5 | $0.00014 | $0.00270 |
| Haiku 4.5 | $0.00007 | $0.00135 |
Grade A, and why
aws-waf-performance-efficiency-skill 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 10d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Apply this skill at design time, when the solution-architect agent has produced a design.md and per-component contracts and is composing the per-pillar review block. The implementation agent re-applies it before transitioning a contract from accepted to implemented. Do not apply this skill to runtime profiling, post-deploy capacity tuning, or live performance triage — its scope is design-time PE assessment.
Trigger conditions:
- The agent is writing the PE review block of
design.mdfor a new or revised feature. - The agent is reviewing a draft contract and needs the PE checklist applied.
- The agent is choosing a compute model (Lambda vs ECS vs Fargate vs EC2 vs Step Functions).
- The agent is verifying that latency targets (p50, p95, p99) are named and measurable.
- The agent is auditing the caching strategy (CloudFront, ElastiCache, DAX, application-tier cache).
Procedure
- Walk the design questions. Apply the questions in
references/pe-design-questions.mdto the artefact under review. A missing answer is a finding, not a passing default. - Scan for anti-patterns. Match the design against the catalogue in
references/pe-antipatterns.md. Each match is recorded with severity and the specific evidence (file path + section). - Run the checklist. Walk
references/pe-checklist.mdend-to-end; every item is satisfied with evidence, deferred with rationale, or flagged as a gap. - Verify compute selection. For every compute component, confirm the runtime choice is justified by the workload's traffic shape (bursty, steady, batch, scheduled) and not by team-default familiarity.
- Verify the load-test plan. A design without a load-test plan named (target throughput, percentile thresholds, ramp profile) is a HIGH gap — performance targets without a verification path are wishes.
- Emit the PE review block. Write the block into
design.mdusingassets/pe-review.md.tmplas the structure: pillar header, design-question summary, anti-patterns matched, checklist outcome, and explicit gap list with severity.
What ships with it
5 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.
- 10d ago First seen · 62 lines · 71 tokens per session scan A 199115c9c848
aws-waf-performance-efficiency-skill is a skill published in the GitHub repository odere-pro/claude-aws-architect (1 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,352 once invoked, about $0.0004 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"…
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.
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.
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.