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 skills/aws-samples/sample-strands-agent-with-agentcore/githubnpx skills add aws-samples/sample-strands-agent-with-agentcore --skill githubgit clone --depth 1 https://github.com/aws-samples/sample-strands-agent-with-agentcoreWhat 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 | $0.00039 | $0.00722 |
| Opus 5 | $0.00019 | $0.00361 |
| Sonnet 5 | $0.00008 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
github 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 2d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub
Available Tools
Read
- github_search_repos(query, max_results?): Search GitHub repositories.
- github_get_repo(owner, repo): Get repository details (description, stars, language, topics).
- github_list_issues(owner, repo, state?, labels?, max_results?): List issues.
state: open | closed | all. - github_get_issue(owner, repo, issue_number): Get a single issue with comments.
- github_list_pulls(owner, repo, state?, max_results?): List pull requests.
- github_get_pull(owner, repo, pull_number): Get a single pull request with diff summary.
- github_get_file(owner, repo, path, ref?): Get file contents.
refdefaults to default branch. - github_search_code(query, max_results?): Search code across GitHub (use
repo:owner/nameto scope).
Write (requires user approval)
- github_create_branch(owner, repo, branch, from_branch?): Create a new branch.
- github_push_files(owner, repo, branch, files, message): Create or update files.
files: list of{path, content}. - github_create_pull_request(owner, repo, title, body, head, base?): Open a pull request.
Usage Guidelines
- Never perform write operations autonomously. Only call
github_create_branch,github_push_files, orgithub_create_pull_requestwhen the user has explicitly requested or approved the action. If the user's intent is ambiguous, ask for confirmation before proceeding. - Always read existing files with
github_get_filebefore modifying them. - Before calling any write tool, explain exactly what will change (branch name, target files, PR details) and wait for user agreement.
- For multi-file changes: create a branch → push all files in one
github_push_filescall → open PR. - Use
github_search_codewithrepo:owner/namequalifier to scope searches to a specific repository.
UI Guidance (from tools-config)
GitHub Tool Usage:
- github_search_repos: Search GitHub repositories by keyword
- github_get_repo: Get repository details (description, stars, language, topics)
- github_list_issues: List issues (state: open|closed|all, filter by labels)
- github_get_issue: Get a single issue with all comments
- github_list_pulls: List pull requests
- github_get_pull: Get a single PR with diff summary
- github_get_file: Read file contents from a repo (specify ref/branch if needed)
- github_search_code: Search code across GitHub (use repo:owner/name to scope)
- github_create_branch: Create a new branch (write — requires approval)
- github_push_files: Create or update files on a branch (write — requires approval)
- github_create_pull_request: Open a pull request (write — requires approval)
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.
- 2d ago First seen · 53 lines · 39 tokens per session scan A f7da8862525d
github is a skill published in the GitHub repository aws-samples/sample-strands-agent-with-agentcore (191 stars, last pushed 6d ago), licensed MIT. It adds 39 tokens to every session and 722 once invoked, about $0.0002 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 skills, from other repositories
draw-image
Generate an image from a text prompt using an OpenAI-compatible image generation API (gpt-image-1-mini or compatible). The image is uploaded to the gofile.io public file sharing service and ONLY the public download page URL is returned. Trigger when user asks to draw, paint, generate, or create an image.
A2A JSON-RPC Call
Call a peer agent's A2A JSON-RPC endpoint. Supports tasks/send (send a task message) and tasks/get (query task status).
Fetch Agent Card
Fetch an A2A agent card JSON from a given endpoint URL. Tries direct GET first, then falls back to /.well-known/agent.json.
Echo Skill Sample
Echo input parameters as JSON.
health-event-impact-assessment
Evaluates AWS Health event impact on application workloads using topology knowledge. Determines blast radius, affected teams, and notification routing. Use this skill when investigating incidents triggered by AWS Health events including scheduled maintenance, operational issues, and service degradation notifications.
a2a-endpoint-validation
Validate an A2A endpoint, Agent Card, health route, and protocol behavior before using it in an agent workflow.