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 strands-agentsgit 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/strands-agents)<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/strands-agents"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/strands-agents/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/ihatesea69/kiro-kit/strands-agents"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/strands-agents.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.01182 |
| Opus 5.5 | $0.00024 | $0.00473 |
| Sonnet 5.5 | $0.00012 | $0.00236 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
strands-agents 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 1mo 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strands Agents
The default agent framework for this workspace. Strands is AWS's lightweight, code-first agent SDK: Bedrock is the default model provider, with Anthropic, OpenAI, and Gemini also supported, and it runs on AWS, on other clouds, or on-prem.
When to Use
- Writing a new agent or chatbot in this workspace
- Adding tools to an existing Strands agent
- Connecting an agent to an MCP server or an AgentCore Gateway
- Building supervisor/worker multi-agent flows
The Model-Driven Tool Loop
Strands does not ask you to draw a graph. You give the model a system prompt and a set of tools; the model decides the sequence.
from strands import Agent, tool
@tool
def lookup_order(order_id: str) -> dict:
"""Return status, items, and delivery estimate for a customer order.
Args:
order_id: The customer-facing order id, e.g. "ORD-10432".
"""
return orders.get(order_id, {"error": "order not found", "retryable": False})
agent = Agent(
model="anthropic.claude-sonnet-4-5-20250929-v1:0",
system_prompt="You are a support assistant. Use tools before answering "
"questions about orders. If a tool returns an error, explain "
"it plainly; never invent an order status.",
tools=[lookup_order],
)
result = agent("Where is ORD-10432?")
The docstring is the tool description the model sees. Write it for the model: what it does, what the arguments mean, and when not to use it.
Streaming
Perceived latency is the product's latency. Stream by default in anything user-facing.
async for event in agent.stream_async(prompt):
if "data" in event:
yield event["data"]
MCP Tools
Point the agent at a Gateway endpoint or a standalone MCP server and its tools
join the loop alongside native @tool functions:
from mcp.client.streamable_http import streamablehttp_client
from strands.tools.mcp import MCPClient
gateway = MCPClient(lambda: streamablehttp_client(
GATEWAY_URL, headers={"Authorization": f"Bearer {access_token}"}))
with gateway:
agent = Agent(tools=[lookup_order, *gateway.list_tools_sync()])
result = agent(prompt)
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.
- 1mo ago First seen · 148 lines · 60 tokens per session scan A 76dd846e6e67
strands-agents is a skill published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,182 once invoked, about $0.0002 per session on Opus 5.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
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…