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 pod-e2egit 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/pod-e2e)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/pod-e2e"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/pod-e2e/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/pod-e2e"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/pod-e2e.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Data Exfiltration · line 101 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00174 | $0.07328 |
| Opus 5.5 | $0.00070 | $0.02931 |
| Sonnet 5.5 | $0.00035 | $0.01466 |
| Haiku 4.5 | $0.00017 | $0.00733 |
Grade A, and why
pod-e2e 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 3d 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 -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:5476/api/sessions # live plane still alive How it starts
The opening of the file, as written. The whole thing — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pod-e2e — test a worktree against an isolated full-stack pod
A worktree's full stack (backend API and frontend SPA) runs as one process
on one port — exactly like a Docker container. The kirocrew pod CLI is the
only interface you need: spin one up, get a {base_url, token} handle, test
against it, tear it down and have the teardown VERIFIED. The live gateway is
never touched.
Quickstart — run the bundled e2e suite
bash <app-skills-dir>/pod-e2e/scripts/pod-e2e.sh <worktree-name> --video
Expected success output — a POD-E2E SUMMARY ending like:
✅ auth — GET /api/sessions → 200 with token, 403 without
✅ playwright — headless chromium loaded dashboard …
result: 2 passed, 0 failed
ARTIFACT_DIR=~/.kirocrew-pods/.e2e-artifacts/<worktree-name>
Exit code = number of failed phases (0 = all green) once phases run. Setup
errors exit before any phase with their own codes (see the flag table below);
a production-port SAFETY refusal exits 1. Then look at the
evidence: Read the screenshots in that ARTIFACT_DIR
(fe-smoke.png, plus any spec screenshots) to confirm the real UI rendered —
not a 403/blank page.
To smoke-test isolation after it finishes:
kirocrew pod ls # should be empty (torn down)
curl -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:5476/api/sessions # live plane still alive
The interface — pod tools if you are an agent, the CLI if you are a human
If you are an agent session, reach for the pod_up / pod_down / pod_status
/ pod_ls MCP tools before a shell. A pod is a systemd --user unit, so every
pod verb needs the systemd user bus. Whether your shell can reach that bus depends
on the sandbox your session runs behind: under Kiro Crew's own sandbox it can (see
security.md, "Scoped user-bus locator forward"), but behind an outer sandbox with
its own user namespace it cannot, and kirocrew pod up then fails with
Permission denied. systemctl --user is-system-running tells you which case you
are in. The tools work either way -- the gateway holds the host bus and does the
systemd part -- so they are the portable choice, and the only one on a host that
denies you the bus.
What ships with it
2 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.
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.
- 3d ago Changed · +8 lines e1caaa36e8bd
- 9d ago Changed · +30 lines e8e938beb0cb
- 12d ago Changed · -1 lines f1a0d2e6a697
- 17d ago Changed · +1 lines 9d9be473eb7d
- 19d ago Changed · -2 lines ae66a66f4468
- 21d ago Changed · +2 lines 72364fc8a5d1
- 27d ago Changed · +6 lines a9356fde8290
- 1mo ago Changed · +83 lines 39503208540e
- 1mo ago Changed · +35 lines b0d4437b3832
- 1mo ago First seen · 338 lines · 174 tokens per session scan A ca2ff5393e87
pod-e2e is a skill published in the GitHub repository kirodotdev/KiroCrew (4,464 stars, last pushed today), licensed Apache-2.0. It adds 174 tokens to every session and 7,328 once invoked, about $0.0007 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
relay-80-100-workflow
Use when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, review-depth fresh-eyes review/fix loops with test hardening, PGlite…
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
capturing-proof
This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…
run-action
Explicit Codex workflow: Execute a learned Maestro flow ("action") by name with optional -e KEY=VALUE parameters. Looks the flow up via packages/rn-dev-agent-core/dist/learned-actions.js (same inventory as $rn-dev-agent:list-learned-actions), then replays it via cdprunaction — auto-repair-aware orchestration with…
build-and-test
Explicit Codex workflow: Build the Expo/React Native app (local or EAS), install it, start Metro, then test a requested feature end-to-end.