artifact-deploy

artifact-deploy is a skill for Claude Code, Codex from kirodotdev/KiroCrew. It costs 74 tokens per session (5,691 once invoked), scanned A, original, Apache-2.0.

A deployment workflow that publishes a pre-built app or other software artifact to the user's own AWS account and returns a public HTTPS link. AWS is Amazon's cloud platform.

In plain words
What is it for?
Deploying a finished app, sharing a demo through a public link, setting a default expiration time, and promoting a temporary deployment to a persistent one.
Why use it?
It removes the manual steps of configuring a deployment and finding the right AWS account and region.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; positional $N argument.

Good fit Deploying a finished app, sharing a demo through a public link, setting a default expiration time, and promoting a temporary deployment to a persistent one.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kirodotdev/kirocrew/artifact-deploy
About the project

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.

kirodotdev/KiroCrew · 4,481 stars · on GitHub · kiro.dev

Install

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.

Any agent
npx skills add kirodotdev/KiroCrew --skill artifact-deploy
Clone the repo
git clone --depth 1 https://github.com/kirodotdev/KiroCrew

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for artifact-deploy

README.md
[![agentmods](https://agentmods.dev/badge/skills/kirodotdev/kirocrew/artifact-deploy/github.svg)](https://agentmods.dev/skills/kirodotdev/kirocrew/artifact-deploy)
Your own site
<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.

agentmods 80×15 button for artifact-deploy

Your own site · 80×15
<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>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,691 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
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.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 11d ago against content hash 0bb3c97c2be8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

The scan reads SKILL.md. This mod also ships 14 executable files (scripts/_common.sh, scripts/attach_backend.py, scripts/cost.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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"])`
src/kiro_crew/deploy/skills/artifact-deploy/SKILL.md · 380 lines

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 /deploy console 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:

  1. User picked one: if the deploy request names a profile (the artifact card's dropdown injects Use the AWS profile "<name>".), use that entry's name/region from the registry. If the name is not in the registry, stop and send the user to the /deploy console to register it -- never deploy with an unregistered profile name.
  2. Registry default: otherwise use the entry named by default.
  3. Legacy fallback: if the core registry doesn't exist, read the old ~/.kiro/crew/apps/deploy-web/data/profiles.json, then its sibling config.json ({"profile", "region"}).
  4. Unconfigured (no registry, no legacy profile): do NOT walk the user through manual profile setup in chat -- link them to the /deploy console (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.

Read the full file on GitHub · 380 lines

Changes

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.

  1. 11d ago Changed · +28 lines 0bb3c97c2be8
  2. 26d ago Changed · -5 lines 73e1fabc9ac7
  3. 1mo ago First seen · 357 lines · 74 tokens per session scan A 816dad7a837c

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories