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 ihatesea69/kiro-kit --skill bedrock-agentcoregit clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/bedrock-agentcore)<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/bedrock-agentcore"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/bedrock-agentcore.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.01535 |
| Opus 5 | $0.00032 | $0.00767 |
| Sonnet 5 | $0.00013 | $0.00307 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
bedrock-agentcore 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 4d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Amazon Bedrock AgentCore
Activate this skill when deploying an agent to AWS or wiring AgentCore components together.
When to Use
- Containerising a Strands / LangGraph / CrewAI / LlamaIndex / ADK agent for hosting
- Choosing a deployment target for an agent (Harness vs Runtime vs Lambda)
- Adding session or long-term memory to a chatbot
- Wiring agent tracing, metrics, and logs
- Hosting an MCP server on AgentCore Runtime
Component Map
| Component | Purpose |
|---|---|
| Runtime | Serverless deployment of an agent container |
| Gateway | Turns APIs, Lambdas, and services into MCP tools (see agentcore-gateway-mcp) |
| Memory | Short-term session context, long-term records |
| Identity | Access control for agents and callers |
| Observability | Traces, metrics, logs for agent runs |
| Code Interpreter | Sandboxed code execution as a tool |
| Browser tool | Headless browsing as a tool |
AgentCore was in preview from July 2025 and reached GA in October 2025 across
nine regions (us-east-1, us-west-2, eu-central-1, ap-southeast-1,
ap-northeast-1 among them). Do not assert that every component is GA —
component availability moves. Check the
release notes
and cite the date you checked.
Choosing a Target
AgentCore Harness (GA June 2026) — no infrastructure, no container, no
orchestration loop. You call CreateHarness and then InvokeHarness. Model
providers include Bedrock, Anthropic, OpenAI, and Gemini. Use it when a hosted
model plus tools is genuinely enough.
AgentCore Runtime — you have agent code and want it hosted. Deliberately framework-agnostic: CrewAI, LangGraph, LlamaIndex, Google ADK, the OpenAI Agents SDK, and Strands Agents all run on it, with any FM in or out of Bedrock (OpenAI, Gemini, Claude, Amazon Nova, Llama, Mistral), speaking MCP and A2A.
Plain Lambda + InvokeModel — it is not really an agent. One model call with
fixed post-processing does not need an agent runtime.
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.
- 4d ago First seen · 167 lines · 63 tokens per session scan A dcacee24b9bc
bedrock-agentcore is a skill published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 19d ago), licensed MIT. It adds 63 tokens to every session and 1,535 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-09-03.
Other skills, from other repositories
awesome-azd-template-submit
Submit an azd template to the awesome-azd gallery. Use when asked to submit, add, or contribute a template to awesome-azd. Requires only a GitHub repository URL — all metadata (title, description, languages, frameworks, Azure services, IaC) is auto-detected by the submission pipeline.
expo-dev-client
Custom development builds with expo-dev-client, build profiles, a custom dev menu, runtime-version compatibility, and EAS Update integration. Triggers on expo-dev-client, dev client, custom dev build, development build, dev menu, expo go, runtime version, debug build, dev launcher, scan qr, dev server.
expo-eas-build
A guide to profile discipline, credentials management, and the build process for EAS Build. Scoped to eas.json configuration, iOS provisioning + push cert, Android keystore + service account, secrets, and monorepo support. Store-submit DETAIL lives in expo-eas-submit.
expo-eas-update
Publishing OTA updates with EAS Update, channels, runtime versions, branch management, and rollback strategy. Triggers on eas update, ota, over-the-air, runtime version, channel, branch, rollback, embedded update, asset selection, expo-updates, hot update, partial release, release cohort.
lizard-core
Core Lizard CLI usage guide. Read this before running any lizard commands. Covers the full app lifecycle (login, init, link, add, up, redeploy, logs, events, status, scale, restart, secrets, domains, run, ssh, metrics), the workspace → project → service model, managed addons (postgres, redis, s3 with auto-public…
setup-deploy
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic.