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 agentmods add instructions/ferdinandobons/awsbedrockagentcoreskill/claude-mdgit clone --depth 1 https://github.com/ferdinandobons/AWSBedrockAgentCoreSkillWrote 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/ferdinandobons/awsbedrockagentcoreskill/claude-md)<a href="https://agentmods.dev/instructions/ferdinandobons/awsbedrockagentcoreskill/claude-md"><img src="https://agentmods.dev/badge/instructions/ferdinandobons/awsbedrockagentcoreskill/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.00727 | $0.00727 |
| Opus 5 | $0.00364 | $0.00364 |
| Sonnet 5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
AWSBedrockAgentCoreSkill 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 6d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project memory - aws-bedrock-agentcore-skill
Claude Code plugin bundling the aws-bedrock-agentcore-skill skill (skills/aws-bedrock-agentcore-skill/):
a source-cited playbook for building AI agents on AWS (Strands Agents, Amazon Bedrock, Bedrock
AgentCore). See README.md. Repo: https://github.com/ferdinandobons/AWSBedrockAgentCoreSkill (public).
Maintenance & freshness - IMPORTANT
This skill documents a fast-moving domain (Bedrock AgentCore went GA in late 2025; features ship monthly). It has a real shelf life. Treat it as self-correcting and well-verified, not guaranteed bug-free - every QA pass so far found real runtime bugs in freshly-added code snippets.
- After ~3–6 months, treat maturity labels, version pins, GA dates, and every "Verify live" item as
SUSPECT until re-checked against the official page in
references/sources.md. - Refresh process: periodically re-run the build/QA workflows - research → build-simulation audit →
full per-file review → snippet verification against official docs. The workflow scripts used to
build and verify this skill live locally in
.aws-research/(gitignored build artifacts; re-runnable or regenerable). The source index is generated bypython3 .aws-research/gen_sources.py. - Bump the version in
.claude-plugin/plugin.jsonon every shipped change; runclaude plugin validate .before committing. - Never hard-code volatile facts (live prices, default quotas, current model IDs/regions) - defer to the AWS console / model cards, as the skill already does.
Authoring rules (when adding or editing content)
- Every best practice and code snippet must carry an inline
_Source:official URL. - New code snippets must be verified against official docs piece by piece (params, shapes/types, enums, ARNs, imports) - do not trust generated code; the QA passes repeatedly caught wrong-param / list-vs-dict / str-vs-bytes / deprecated-API bugs.
- Provenance: official sources only -
docs.aws.amazon.com,strandsagents.com, official AWS GitHub orgs (aws/awslabs/aws-samples/aws-ia), the official Terraform registry (hashicorp/aws,hashicorp/awscc), andboto3/pypi/npm. The two non-AWS sources (the A2A protocol spec and Langfuse as an optional OTEL backend) are labelled as such; third-party blogs are excluded. - Keep
SKILL.mda router (decision tree + playbooks); put depth inreferences/. On any conflict, thereferences/file wins over theassets/matrices and over theSKILL.mdsummary. - After adding sources, regenerate
references/sources.mdand re-run the link check before committing.
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.
- 6d ago First seen · 46 lines · 727 tokens per session scan A 508e5d57446d
AWSBedrockAgentCoreSkill CLAUDE.md is an instructions file published in the GitHub repository ferdinandobons/AWSBedrockAgentCoreSkill (209 stars, last pushed 3mo ago), licensed MIT. It adds 727 tokens to every session, about $0.0036 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-30.
Other instructions, from other repositories
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).
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.
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.
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.
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).