Agent skill

AWS Strands Agents Agentcore

by sammcj in sammcj/agentic-coding

A skill your agent uses when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents.

Apache-2.0Auto-check passedDevOps & Cloud

Install AWS Strands Agents Agentcore

skills CLI
$ npx skills add sammcj/agentic-coding --skill aws-strands-agents-agentcore -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sammcj/agentic-coding aws-strands-agents-agentcore --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sammcj/agentic-coding.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Skills_disabled/aws-strands-agents-agentcore .claude/skills/aws-strands-agents-agentcore && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
aws-strands-agents-agentcore
GitHub stars
162
Token cost
~3k tokens
SKILL.md length
787 words
Files
6 (incl. references)
Skills in repo
64
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents.

  • Works in 4 steps: Transport: MUST use streamable-http (NOT… → Endpoint: MUST be at 0.0.0.0:8000/mcp → Deployment: MUST be ECS/Fargate or… → …
  • Working with AWS Strands Agents SDK
  • SKILL.md covers Overview, Quick Start Decision Tree, Critical Constraints and Deployment Decision Matrix, plus 9 more sections
  • Calls aws

What it does

AWS Strands Agents Agentcore is an agent skill from sammcj/agentic-coding. Use when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents. Provides architecture guidance, implementation patterns, deployment strategies, observability, quality evaluations, multi-agent orchestration, and MCP server integration.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/architecture.md`, `references/evaluations.md` and `references/limitations.md`).

It sits in DevOps & Cloud, covering Multi-agent orchestration, Observability and Building AI agents. It works with Amazon Web Services, Model Context Protocol and Amazon Bedrock. The repository describes itself as: Agentic Coding Rules, Templates etc... The licence is Apache-2.0.

When your agent uses it

  • Working with AWS Strands Agents SDK
  • Amazon Bedrock AgentCore platform for building AI agents

Example prompts

  • “/aws-strands-agents-agentcore”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Transport: MUST use streamable-http (NOT stdio)
  2. Endpoint: MUST be at 0.0.0.0:8000/mcp
  3. Deployment: MUST be ECS/Fargate or AgentCore Runtime (NEVER Lambda)
  4. Headers: Must accept application/json and text/event-stream

What it can do on your machine

Read from SKILL.md and the folder at commit 2f25ced. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • aws

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use aws, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

AWS Strands Agents Agentcore loads about 3k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 787 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sammcj/agentic-coding at commit 2f25ced, republished under its Apache-2.0 licence (© sammcj). 787 words, ~2,956 tokens.

Download SKILL.mdSave it as .claude/skills/aws-strands-agents-agentcore/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
aws-strands-agents-agentcore
description
Use when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents. Provides architecture guidance, implementation patterns, deployment strategies, observability, quality evaluations, multi-agent orchestration, and MCP server integration.

AWS Strands Agents & AgentCore

Overview

AWS Strands Agents SDK: Open-source Python framework for building AI agents with model-driven orchestration (minimal code, model decides tool usage)

Amazon Bedrock AgentCore: Enterprise platform for deploying, operating, and scaling agents in production

Relationship: Strands SDK runs standalone OR with AgentCore platform services. AgentCore is optional but provides enterprise features (8hr runtime, streaming, memory, identity, observability).


Quick Start Decision Tree

What are you building?

Single-purpose agent:

  • Event-driven (S3, SQS, scheduled) → Lambda deployment
  • Interactive with streaming → AgentCore Runtime
  • API endpoint (stateless) → Lambda

Multi-agent system:

  • Deterministic workflow → Graph Pattern
  • Autonomous collaboration → Swarm Pattern
  • Simple delegation → Agent-as-Tool Pattern

Tool/Integration Server (MCP):

  • ALWAYS deploy to ECS/Fargate or AgentCore Runtime
  • NEVER Lambda (stateful, needs persistent connections)

See architecture.md for deployment examples.


Critical Constraints

MCP Server Requirements
  1. Transport: MUST use streamable-http (NOT stdio)
  2. Endpoint: MUST be at 0.0.0.0:8000/mcp
  3. Deployment: MUST be ECS/Fargate or AgentCore Runtime (NEVER Lambda)
  4. Headers: Must accept application/json and text/event-stream

Why: MCP servers are stateful and need persistent connections. Lambda is ephemeral and unsuitable.

See limitations.md for details.

Tool Count Limits
  • Models struggle with > 50-100 tools
  • Solution: Implement semantic search for dynamic tool loading

See patterns.md for implementation.

Token Management
  • Claude 4.5: 200K context (use ~180K max)
  • Long conversations REQUIRE conversation managers
  • Multi-agent costs multiply 5-10x

See limitations.md for strategies.


Deployment Decision Matrix

ComponentLambdaECS/FargateAgentCore Runtime
Stateless Agents✅ Perfect❌ Overkill❌ Overkill
Interactive Agents❌ No streaming⚠️ Possible✅ Ideal
MCP Servers❌ NEVER✅ Standard✅ With features
Duration< 15 minutesUnlimitedUp to 8 hours
Cold StartsYes (30-60s)NoNo

Multi-Agent Pattern Selection

PatternComplexityPredictabilityCostUse Case
Single AgentLowHigh1xMost tasks
Agent as ToolLowHigh2-3xSimple delegation
GraphHighVery High3-5xDeterministic workflows
SwarmMediumLow5-8xAutonomous collaboration

Recommendation: Start with single agents, evolve as needed.

See architecture.md for examples.


When to Read Reference Files

patterns.md
  • Base agent factory patterns (reusable components)
  • MCP server registry patterns (tool catalogues)
  • Semantic tool search (> 50 tools)
  • Tool design best practices
  • Security patterns
  • Testing patterns
observability.md
  • AWS AgentCore Observability Platform setup
  • Runtime-hosted vs self-hosted configuration
  • Session tracking for multi-turn conversations
  • OpenTelemetry setup
  • Cost tracking hooks
  • Production observability patterns
evaluations.md
  • AWS AgentCore Evaluations - Quality assessment with LLM-as-a-Judge
  • 13 built-in evaluators (Helpfulness, Correctness, GoalSuccessRate, etc.)
  • Custom evaluators with your own prompts and models
  • Online (continuous) and on-demand evaluation modes
  • CloudWatch integration and alerting
limitations.md
  • MCP server deployment issues
  • Tool selection problems (> 50 tools)
  • Token overflow
  • Lambda limitations
  • Multi-agent cost concerns
  • Throttling errors
  • Cold start latency

#-Driven Philosophy

Key Concept: Strands Agents delegates orchestration to the model rather than requiring explicit control flow code.

python
# Traditional: Manual orchestration (avoid)
while not done:
    if needs_research:
        result = research_tool()
    elif needs_analysis:
        result = analysis_tool()

# Strands: Model decides (prefer)
agent = Agent(
    system_prompt="You are a research analyst. Use tools to answer questions.",
    tools=[research_tool, analysis_tool]
)
result = agent("What are the top tech trends?")
 automatically orchestrates: research_tool → analysis_tool → respond

Selection

Primary Provider: Anthropic Claude via AWS Bedrock

Model ID Format: anthropic.claude-{model}-{version}

Current Models (as of January 2025):

  • anthropic.claude-sonnet-4-5-20250929-v1:0 - Production
  • anthropic.claude-haiku-4-5-20251001-v1:0 - Fast/economical
  • anthropic.claude-opus-4-5-20250514-v1:0 - Complex reasoning

Check Latest Models:

bash
aws bedrock list-foundation-models --by-provider anthropic \
  --query 'modelSummaries[*].[modelId,modelName]' --output table

Quick Examples

Basic Agent
python
from strands import Agent
from strands.models import BedrockModel
from strands.session import DynamoDBSessionManager
from strands.agent.conversation_manager import SlidingWindowConversationManager

agent = Agent(
    agent_id="my-agent",
    model=BedrockModel(model_id="anthropic.claude-sonnet-4-5-20250929-v1:0"),
    system_prompt="You are helpful.",
    tools=[tool1, tool2],
    session_manager=DynamoDBSessionManager(table_name="sessions"),
    conversation_manager=SlidingWindowConversationManager(max_messages=20)
)

result = agent("Process this request")

See patterns.md for base agent factory patterns.

Show full SKILL.md (317 more words)Show less
MCP Server (ECS/Fargate)
python
from mcp.server import FastMCP
import psycopg2.pool

# Persistent connection pool (why Lambda won't work)
db_pool = psycopg2.pool.SimpleConnectionPool(minconn=1, maxconn=10, host="db.internal")

mcp = FastMCP("Database Tools")

@mcp.tool()
def query_database(sql: str) -> dict:
    conn = db_pool.getconn()
    try:
        cursor = conn.cursor()
        cursor.execute(sql)
        return {"status": "success", "rows": cursor.fetchall()}
    finally:
        db_pool.putconn(conn)

# CRITICAL: streamable-http mode
if __name__ == "__main__":
    mcp.run(transport="streamable-http", host="0.0.0.0", port=8000)

See architecture.md for deployment details.

Tool Error Handling
python
from strands import tool

@tool
def safe_tool(param: str) -> dict:
    """Always return structured results, never raise exceptions."""
    try:
        result = operation(param)
        return {"status": "success", "content": [{"text": str(result)}]}
    except Exception as e:
        return {"status": "error", "content": [{"text": f"Failed: {str(e)}"}]}

See patterns.md for tool design patterns.

Observability

AgentCore Runtime (Automatic):

python
# Install with OTEL support
# pip install 'strands-agents[otel]'
# Add 'aws-opentelemetry-distro' to requirements.txt

from bedrock_agentcore.runtime import BedrockAgentCoreApp

app = BedrockAgentCoreApp()
agent = Agent(...)  # Automatically instrumented

@app.entrypoint
def handler(payload):
    return agent(payload["prompt"])

Self-Hosted:

bash
export AGENT_OBSERVABILITY_ENABLED=true
export OTEL_PYTHON_DISTRO=aws_distro
export OTEL_RESOURCE_ATTRIBUTES="service.name=my-agent"

opentelemetry-instrument python agent.py

General OpenTelemetry:

python
from strands.observability import StrandsTelemetry

# Development
telemetry = StrandsTelemetry().setup_console_exporter()

# Production
telemetry = StrandsTelemetry().setup_otlp_exporter()

See observability.md for detailed patterns.


Session Storage Selection

Local dev         → FileSystem
Lambda agents     → S3 or DynamoDB
ECS agents        → DynamoDB
Interactive chat  → AgentCore Memory
Knowledge bases   → AgentCore Memory

See architecture.md for storage backend comparison.


When to Use AgentCore Platform vs SDK Only

Use Strands SDK Only
  • Simple, stateless agents
  • Tight cost control required
  • No enterprise features needed
  • Want deployment flexibility
Use Strands SDK + AgentCore Platform
  • Need 8-hour runtime support
  • Streaming responses required
  • Enterprise security/compliance
  • Cross-session intelligence needed
  • Want managed infrastructure

See architecture.md for platform service details.


Common Anti-Patterns

  1. ❌ Overloading agents with > 50 tools → Use semantic search
  2. ❌ No conversation management → Implement SlidingWindow or Summarising
  3. ❌ Deploying MCP servers to Lambda → Use ECS/Fargate
  4. ❌ No timeout configuration → Set execution limits everywhere
  5. ❌ Ignoring token limits → Implement conversation managers
  6. ❌ No cost monitoring → Implement cost tracking from day one

See patterns.md and limitations.md for details.


Production Checklist

Before deploying:

  • Conversation management configured
  • AgentCore Observability enabled or OpenTelemetry configured
  • AgentCore Evaluations configured for quality monitoring
  • Observability hooks implemented
  • Cost tracking enabled
  • Error handling in all tools
  • Security permissions validated
  • MCP servers deployed to ECS/Fargate
  • Timeout limits set
  • Session backend configured (DynamoDB for production)
  • CloudWatch alarms configured

Reference Files Navigation

  • architecture.md - Deployment patterns, multi-agent orchestration, session storage, AgentCore services
  • patterns.md - Foundation components, tool design, security, testing, performance optimisation
  • limitations.md - Known constraints, workarounds, mitigation strategies, challenges
  • observability.md - AgentCore Observability platform, ADOT, GenAI dashboard, OpenTelemetry, hooks, cost tracking
  • evaluations.md - AgentCore Evaluations, built-in evaluators, custom evaluators, quality monitoring

Key Takeaways

  1. MCP servers MUST use streamable-http, NEVER Lambda
  2. Use semantic search for > 15 tools
  3. Always implement conversation management
  4. Multi-agent costs multiply 5-10x (track from day one)
  5. Set timeout limits everywhere
  6. Error handling in tools is non-negotiable
  7. Lambda for stateless, AgentCore for interactive
  8. AgentCore Observability and Evaluations for production
  9. Start simple, evolve complexity
  10. Security by default
  11. Separate config from code

© sammcj, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in Skills_disabled/aws-strands-agents-agentcore of sammcj/agentic-coding.

  • SKILL.md
  • references/architecture.md
  • references/evaluations.md
  • references/limitations.md
  • references/observability.md
  • references/patterns.md

Open the folder on GitHubat commit 2f25ced

Compare with similar skills

AWS Strands Agents Agentcore next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

AWS Strands Agents Agentcore compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AWS Strands Agents Agentcore this skillsammcj/agentic-coding162—~3kAutomated safety check: PassApache-2.0
AWS Agentic AIzxkane/aws-skills367—~2.5kAutomated safety check: PassMIT
Hcls Deploy Agentaws-samples/amazon-bedrock-agents-healthcare-lifesciences274—~813Automated safety check: PassMIT-0
AWS Agentic AICommandCodeAI/agent-skills133—~1.5kAutomated safety check: PassMIT
AWS Cdk Developmentzxkane/aws-skills3672 repos~2.5kAutomated safety check: PassMIT
Deploy Observabilityaliyun/alibabacloud-observability-mcp-server166—~2.6kAutomated safety check: NotesNone

Similar skills

  • AWS Agentic AI

    zxkane/aws-skills

    AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale.

    367 GitHub stars~2.5k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Hcls Deploy Agent

    aws-samples/amazon-bedrock-agents-healthcare-lifesciences

    Official

    A skill your agent uses when a developer wants to deploy an HCLS agent to Amazon Bedrock AgentCore, configure Gateway tools as MCP endpoints, set up authentication with Cognito, configure memory, or…

    274 GitHub stars~813 tokensUpdated 8 days ago
    DevOps & CloudAuto-check passed
  • AWS Agentic AI

    CommandCodeAI/agent-skills

    AWS Bedrock AgentCore comprehensive expert for deploying and managing all AgentCore services.

    133 GitHub stars~1.5k tokensUpdated 7 mo ago
    DevOps & CloudAuto-check passed
  • AWS Cdk Development

    zxkane/aws-skills

    AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.

    367 GitHub starsUsed in 2 repos~2.5k tokens
    DevOps & CloudAuto-check passed
  • Deploy Observability

    aliyun/alibabacloud-observability-mcp-server

    Deploy, start, and update the Alibaba Cloud Observability MCP Server (阿里云可观测 MCP Server).

    166 GitHub stars~2.6k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes
  • AWS Cost Operations

    zxkane/aws-skills

    AWS cost optimization, monitoring, and operational excellence expert.

    367 GitHub stars~2.4k tokensUpdated 3 mo ago
    DevOps & CloudAuto-check passed

More from sammcj/agentic-coding

All 64 skills in this repo
  • Yue2 Music

    sammcj/agentic-coding

    A skill your agent uses when generating songs with YuE2, covering a recording via SheetSage2 audio-to-ABC, editing a score or lyrics with melody preservation, or building a reproducible listening…

    162 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed
  • Bento Slides

    sammcj/agentic-coding

    A skill your agent uses when creating or editing Bento (.bento.html) slide decks, including any request for a single-file HTML slide deck.

    162 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Idrive Backup

    sammcj/agentic-coding

    A skill your agent uses whenever the user wants you to manage, discuss or diagnose iDrive Backup configuration on macOS

    162 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check: notes
  • Piper Tts Training

    sammcj/agentic-coding

    Train custom TTS voices for Piper (ONNX format) using fine-tuning or from-scratch approaches.

    162 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • PPTX To Md

    sammcj/agentic-coding

    Convert a PPTX slide deck into per-slide markdown that preserves both the verbatim text and the meaning of embedded screenshots, diagrams and charts in their original layout positions.

    162 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Skill Creator Primer

    sammcj/agentic-coding

    You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill.

    162 GitHub stars~9.8k tokensUpdated yesterday
    Auto-check passed

Questions about AWS Strands Agents Agentcore

What does AWS Strands Agents Agentcore do?

A skill your agent uses when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents. AWS Strands Agents Agentcore is an agent skill from sammcj/agentic-coding. Use when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents.

When should I use AWS Strands Agents Agentcore?

AWS Strands Agents Agentcore fits situations like: working with AWS Strands Agents SDK; amazon Bedrock AgentCore platform for building AI agents.

How do I install AWS Strands Agents Agentcore in Claude Code?

Run `npx skills add sammcj/agentic-coding --skill aws-strands-agents-agentcore -a claude-code`. Or copy the skill folder (Skills_disabled/aws-strands-agents-agentcore in sammcj/agentic-coding) into .claude/skills/aws-strands-agents-agentcore in your project. Claude Code loads it when a task matches its description.

How do I install AWS Strands Agents Agentcore in Codex?

Run `npx skills add sammcj/agentic-coding --skill aws-strands-agents-agentcore -a codex`. Or copy the skill folder (Skills_disabled/aws-strands-agents-agentcore in sammcj/agentic-coding) into .agents/skills/aws-strands-agents-agentcore in your project. Codex loads it when a task matches its description.

Can I use AWS Strands Agents Agentcore in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sammcj/agentic-coding --skill aws-strands-agents-agentcore -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aws-strands-agents-agentcore, .gemini/skills/aws-strands-agents-agentcore, .github/skills/aws-strands-agents-agentcore and .opencode/skills/aws-strands-agents-agentcore in your project.

What does AWS Strands Agents Agentcore need to run?

Going by SKILL.md and its folder, AWS Strands Agents Agentcore needs the command-line tools its instructions call (aws). Our summary lists: Python 3.

Does AWS Strands Agents Agentcore access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is AWS Strands Agents Agentcore safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does AWS Strands Agents Agentcore use?

AWS Strands Agents Agentcore is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does AWS Strands Agents Agentcore use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.2k tokens, read only when the agent opens those files.

What are the alternatives to AWS Strands Agents Agentcore?

Skills that share tags, products or a category with AWS Strands Agents Agentcore: AWS Agentic AI (zxkane/aws-skills, 367 stars), Hcls Deploy Agent (aws-samples/amazon-bedrock-agents-healthcare-lifesciences, 274 stars), AWS Agentic AI (CommandCodeAI/agent-skills, 133 stars) and AWS Cdk Development (zxkane/aws-skills, 367 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AWS Strands Agents Agentcore?

sammcj (a GitHub user) maintains it in sammcj/agentic-coding, which has 162 GitHub stars. The repository holds 64 skills in this directory. The repository was last updated on October 9, 2026.

Source: sammcj/agentic-coding on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.