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 hey-iam-ryan/kiro-power-aws-knowledge-plus --skill aws-researchgit clone --depth 1 https://github.com/hey-iam-ryan/kiro-power-aws-knowledge-plusWrote 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/hey-iam-ryan/kiro-power-aws-knowledge-plus/aws-research)<a href="https://agentmods.dev/skills/hey-iam-ryan/kiro-power-aws-knowledge-plus/aws-research"><img src="https://agentmods.dev/badge/skills/hey-iam-ryan/kiro-power-aws-knowledge-plus/aws-research/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/hey-iam-ryan/kiro-power-aws-knowledge-plus/aws-research"><img src="https://agentmods.dev/badge/skills/hey-iam-ryan/kiro-power-aws-knowledge-plus/aws-research.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.00095 | $0.00778 |
| Opus 5 | $0.00048 | $0.00389 |
| Sonnet 5 | $0.00019 | $0.00156 |
| Haiku 4.5 | $0.00010 | $0.00078 |
Grade A, and why
aws-research 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS knowledge research
This power covers three sources the official AWS Knowledge MCP Server does not index. It is a supplement, not a replacement. Route the question first.
Step 1: Route the question
| The question is about | Use |
|---|---|
| AWS service behaviour, API and CLI reference, quotas, Well-Architected, whitepapers | Whichever tool in this session reaches the official AWS documentation corpus |
| An error message, or "why doesn't this work in practice" | search_aws_knowledge(sources=["repost"]) |
| Kiro itself: steering, hooks, specs, powers, MCP setup, CLI, changelog | search_aws_knowledge(sources=["kiro"]) |
| AWS Builders' Library, or a community write-up | search_aws_knowledge(sources=["builder"]) |
| Unsure | search_aws_knowledge(query) with no sources, then read the best hits |
Do not use this power for AWS documentation, AWS blog posts, What's New
announcements or re:Post Knowledge Center articles. Those are indexed by the
official AWS Knowledge MCP Server, which returns better results for them. Call
list_sources() to confirm the division, and see
references/source-guide.md for questions that need a kind of source none of
these three provide.
Step 2: Search, then read
search_aws_knowledge returns short snippets on purpose. Snippets are for
choosing what to read, never for answering. Pick the 2-3 most promising hits and
pass each URL to read_aws_content.
If a page is truncated, the response tells you the start_index to resume from.
Continue only when the part you need is actually missing.
Step 3: Weigh the sources honestly
Official documentation outranks everything else on facts. When a re:Post thread contradicts the docs, say so explicitly rather than silently preferring one.
For re:Post threads, read the signals the tool returns: an accepted answer with upvotes outweighs an unanswered one, and service behaviour changes, so check the date before repeating advice. An unanswered thread still tells you someone else hit the same wall — report that as a symptom, not as a solution.
What ships with it
1 file 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 · 64 lines · 95 tokens per session scan A 9f3b2253a696
aws-research is a skill published in the GitHub repository hey-iam-ryan/kiro-power-aws-knowledge-plus (0 stars, last pushed 18d ago), licensed Apache-2.0. It adds 95 tokens to every session and 778 once invoked, about $0.0005 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
hyperpod-node-debugger
Diagnose and remediate per-node issues on a HyperPod cluster (EKS or Slurm) — a specific node is unhealthy, unresponsive, stuck, or needs replacing. Covers on-node EFA, GPU / accelerator hardware (XID, ECC, NVLink, row-remap, DCGM), Slurm node down/drained, disk and memory pressure, per-node lifecycle-script failures…
aws-lambda-managed-instances
Evaluate, configure, and migrate workloads to AWS Lambda Managed Instances (LMI). Triggers on: Lambda Managed Instances, LMI, capacity provider, multi-concurrency Lambda, dedicated instance Lambda, EC2-backed Lambda, cold start elimination, Graviton Lambda, instance type for Lambda, scheduled scaling for LMI, Lambda…
aws-architecture-diagram
Generate validated AWS architecture diagrams as draw.io XML using official AWS4 icon libraries. Use this skill whenever the user wants to create, generate, or design AWS architecture diagrams, cloud infrastructure diagrams, or system design visuals. Also triggers for requests to visualize existing infrastructure from…
hyperpod-performance-debugger
Diagnose performance issues on Amazon SageMaker HyperPod clusters — uneven NCCL bandwidth across nodes and poor filesystem throughput. Read-only. Surfaces host-side signals (Xid, ECC, NVLink, EFA reachability, FSx saturation) and routes to the appropriate sibling skill (hyperpod-node-debugger, hyperpod-nccl…
amplify-workflow
Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB including schema modeling, enum types, relationships, authorization rules), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue…
hyperpod-cluster-debugger
Diagnose and remediate cluster-wide HyperPod (EKS or Slurm) problems — creation / deployment failures (CloudFormation, EFA health check, lifecycle scripts, capacity), EKS access, node replacement, CloudFormation nested-stack errors, post-maintenance rollback state, dangling nodes, autoscaler conflicts. Includes…