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/kirodotdev/kirocrew/deploy-webnpx skills add kirodotdev/KiroCrew --skill deploy-webgit clone --depth 1 https://github.com/kirodotdev/KiroCrewWhat 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.00094 | $0.01270 |
| Opus 5 | $0.00047 | $0.00635 |
| Sonnet 5 | $0.00019 | $0.00254 |
| Haiku 4.5 | $0.00009 | $0.00127 |
Grade A, and why
deploy-web 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deploy-web — publish artifacts to your own AWS
deploy-web is a built-in app. The deploy/recall/destroy mechanics run as deterministic
Python in the app backend (it shells to the aws CLI with --profile). This skill is
the chat-native front door + the AI-guided one-time setup. You never read, store,
or manage credentials, and you never perform an IAM write — you generate policy text the
user applies themselves (design Option A).
UI entry point (Route B, design §1.1): in the dashboard, publishing is initiated from an artifact's page (Publish → "Publish to public web (your AWS)"), which calls the
POST /deployendpoint below. The Artifact Deploy app page is a management console — guided setup, health check, and Manage Sites (Recall/Destroy) — it has no publish form. The chat-native path (this skill) is unchanged and still drives the same backend endpoints.
Hard rules (never violate)
- Never run
aws configure,aws sso login,ada, or any credential-establishing command on the user's behalf. Tell them to run it themselves. - Never create/attach/modify IAM roles or policies. Generate the JSON; the user applies it.
- Never auto-approve deploy / recall / destroy. Each is per-invocation confirmed.
- Publishing makes content world-readable. Always state this before deploying.
Backend endpoints (call via the gateway; do not reinvent the aws flow)
GET /api/deploy/config→{profile, region}PUT /api/deploy/config{profile, region}→ saves the profile name onlyGET /api/deploy/iam-policy[?custom_domain=1]→ least-privilege policy JSONPOST /api/deploy/verify→ read-only reachability (NOT full verification)POST /api/deploy/deploy{site_id, artifact_slug|local_dir, confirm, override_scan}POST /api/deploy/recall{site_id, confirm}POST /api/deploy/destroy{site_id, confirm}GET /api/deploy/list→ live site list (status from the distribution)
Guided installation (one-time, ~10–15 min — runs once, reused forever)
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 · 76 lines · 94 tokens per session scan A 60c9b37ea299
deploy-web is a skill published in the GitHub repository kirodotdev/KiroCrew (3,532 stars, last pushed today), licensed Apache-2.0. It adds 94 tokens to every session and 1,270 once invoked, about $0.0005 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
copilotkit-setup
Use when adding CopilotKit to an existing project or bootstrapping a new CopilotKit project from scratch. Covers framework detection, package installation, runtime wiring (managed Intelligence or self-hosted SSE), provider setup, and first working chat integration.
setup-slack-channel
Use for the PROVIDER half of getting a locally running CopilotKit Channels agent to answer in Slack, when no Slack app exists yet — setting up a Channels bot in Slack for the first time, creating the Slack app and its tokens, attaching it to a managed Intelligence Channel, or when a Channel reports setuprequired, sits…
copilotkit-channels
Use for the CODE half of a managed Intelligence Channel with Slack or Microsoft Teams: customising the Channel a CLI-scaffolded project already ships, or — for a project the CLI did not generate — writing the Channel declaration, the long-running host, and the awaited activation call. Teams provider setup is in scope…
runtime
@copilotkit/runtime — mount a fetch-native CopilotRuntime on any JS server, wire middleware, pick an AgentRunner, instantiate BuiltInAgent (Factory Mode with TanStack AI is the preferred default) or plug in any of 12 external agent frameworks (Mastra, LangGraph, CrewAI Crews/Flows, PydanticAI, ADK, LlamaIndex, Agno…
copilotkit-integrations
Use when wiring an external agent framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, or others) into a CopilotKit application via the AG-UI protocol.
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.