Kiro Crew is a persistent development workspace where agents continue multi-step software work across sessions, schedules, and connected interfaces. Developers use it locally or remotely through a desktop app, web dashboard, CLI, Slack, or Discord, with unattended tasks and recurring jobs. The catalogue contains skills and instructions for working with this workspace.
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 kirodotdev/KiroCrew --skill artifact-deploygit clone --depth 1 https://github.com/kirodotdev/KiroCrewWrote 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/kirodotdev/kirocrew/artifact-deploy)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/artifact-deploy"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/artifact-deploy/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/kirodotdev/kirocrew/artifact-deploy"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/artifact-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 32 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00074 | $0.05691 |
| Opus 5.5 | $0.00030 | $0.02276 |
| Sonnet 5.5 | $0.00015 | $0.01138 |
| Haiku 4.5 | $0.00007 | $0.00569 |
Grade A, and why
artifact-deploy scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -d` without `-H application/json`). Calling `json.loads(event["body"])` How it starts
The opening of the file, as written. The whole thing — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kiro Crew One-Click Deploy (MVP)
Shipped by Kiro Crew core (
src/kiro_crew/deploy/), not by an installable app. Gateway startup copies this skill into~/.kiro/crew/skills/artifact-deploy/. The/deployconsole owns AWS profile setup, verification, pending confirmations, and the fleet/cost view; this skill prepares and previews deployments.
AWS config -- resolve the profile from the core registry, don't ask
The Artifact Deploy core module owns the AWS configuration as a multi-profile
registry at ~/.kiro/crew/deploy/profiles.json
({"profiles": [{"name", "region", ...}], "default": "<name>"}). Resolve the
deploy profile in this order, before asking the user anything:
- User picked one: if the deploy request names a profile (the artifact
card's dropdown injects
Use the AWS profile "<name>".), use that entry'sname/regionfrom the registry. If the name is not in the registry, stop and send the user to the/deployconsole to register it -- never deploy with an unregistered profile name. - Registry default: otherwise use the entry named by
default. - Legacy fallback: if the core registry doesn't exist, read the old
~/.kiro/crew/apps/deploy-web/data/profiles.json, then its siblingconfig.json({"profile", "region"}). - Unconfigured (no registry, no legacy profile): do NOT walk the user
through manual profile setup in chat -- link them to the
/deployconsole (Artifacts -> Artifact Deploy), which has the Profiles control plane (register / create + Verify access + IAM policy generator). Resume once a profile exists.
After a successful deploy, back-fill webapp_metadata.deploy_target.profile
with the profile NAME actually used, so the fleet table and the artifact's
control card show which identity owns the deployment.
This replaces the old "pick the AWS profile" step: profiles are managed once in
the console, then every deploy (static publish or fullstack webapp) reuses them.
Reachability is confirmed by the human with Verify access on /deploy
(POST /api/deploy/verify, an STS read). That route refuses MCP/internal
callers, so an agent cannot call it; the deploy_artifact preview reports the
resolved profile and region instead.
What ships with it
20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- MIGRATION.md 2.8 KB
- scripts/_common.sh 7.6 KB runs code
- scripts/attach_backend.py 17 KB runs code
- scripts/cost.sh 7.8 KB runs code
- scripts/deploy-app.sh 2.2 KB runs code
- scripts/deploy-backend.sh 7.6 KB runs code
- scripts/deploy.sh 13 KB runs code
- scripts/detach_backend.py 6.0 KB runs code
- scripts/install-reaper.sh 4.0 KB runs code
- scripts/list.sh 1.8 KB runs code
- scripts/persist.sh 1.3 KB runs code
- scripts/reaper_lambda/index.py 29 KB runs code
- scripts/reaper.sh 15 KB runs code
- scripts/teardown.sh 3.0 KB runs code
- templates/app-apigw-ddb.yaml 10 KB
- templates/app-apigw.yaml 9.1 KB
- templates/app-lambda.yaml 2.7 KB
- templates/base-stack.yaml 17 KB
- templates/handler-example.py 2.2 KB runs code
- templates/reaper.yaml 11 KB
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.
- 11d ago Changed · +28 lines 0bb3c97c2be8
- 26d ago Changed · -5 lines 73e1fabc9ac7
- 1mo ago First seen · 357 lines · 74 tokens per session scan A 816dad7a837c
artifact-deploy is a skill published in the GitHub repository kirodotdev/KiroCrew (4,481 stars, last pushed today), licensed Apache-2.0. It adds 74 tokens to every session and 5,691 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
vigilante-issue-implementation-on-terraform
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Terraform repository with fmt, validate, and secret-safe infrastructure guidance.
tcapi
A helper for managing Tencent Cloud resources through Tencent Cloud's command-line API tool. Tencent Cloud is a cloud-services provider offering products such as virtual servers, storage, networks, and containers.
cost-efficiency-analyzer
Analyzes cost structure, cost efficiency, and expense management from P&L data. Use when the user asks about costs, expenses, COGS, operating expenses, cost ratios, cost control, spending efficiency, margin compression from cost side, or wants to understand where money is going. Also use for "are we spending too…
sector-rotation
Identify which market sectors to overweight or underweight based on current macro conditions and sector performance data.
trend-analysis
Analyze price and volume trends for one or more stocks to determine momentum direction and key technical levels.
deploying-to-staging-environment
Use when deploying changes to staging across relay, relay-dashboard, and relay-cloud repos - coordinates multi-repo branch syncing using git worktrees, automatically triggers staging deployments via GitHub Actions.