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 kirocrew-commandsgit 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/kirocrew-commands)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/kirocrew-commands"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/kirocrew-commands.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 9 findings, 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 Privilege Escalation · line 172 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Tool Misuse · line 32 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Excessive Agency · line 45 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 46 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Privilege Escalation · line 66 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Excessive Agency · line 146 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 522 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 179 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.
- medium Rogue Agent · line 238 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.00036 | $0.08259 |
| Opus 5 | $0.00018 | $0.04130 |
| Sonnet 5 | $0.00007 | $0.01652 |
| Haiku 4.5 | $0.00004 | $0.00826 |
Grade B, and why
kirocrew-commands scanned grade B 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| `kirocrew service install` | Install and start as system service (sudo on Linux) | How it starts
The opening of the file, as written. The whole thing — 542 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kiro Crew CLI Reference
Setup & System
| Command | Description |
|---|---|
kirocrew setup |
Interactive wizard — install agent config (messaging channels connect later) |
kirocrew setup --slack |
Also run the guided Slack credential setup (opt-in; ignored with --agent-only) |
kirocrew setup --agent-only |
Only install kiro-cli agent config, skip the other wizard steps |
kirocrew setup --clean |
Fresh install — don't merge from existing config |
kirocrew doctor |
Verify Kiro Crew setup (checks all dependencies) |
kirocrew doctor --bundle |
Collect logs + crash reports into a redacted diagnostics zip |
kirocrew update |
Update Kiro Crew to the latest version |
kirocrew update approve |
Approve a pending in-app update armed from the dashboard |
kirocrew update --force |
Discard local commits when a git checkout has diverged from upstream (git installs only) |
kirocrew --version |
Print installed version |
kirocrew sandbox status |
Report whether this launch is covered by the userns AppArmor profile |
kirocrew sandbox install-profile |
Attach the profile to this app (sudo; --path P for an explicit executable) |
kirocrew sandbox remove-profile |
Unload and remove the profile (sudo) |
update --force is destructive on a git install: the hard reset discards local
commits, recoverable only from git reflog. The sandbox verbs matter only on
hosts with kernel.apparmor_restrict_unprivileged_userns=1 (Ubuntu 23.10+ and
derivatives) and are no-ops everywhere else; --path is refused for
world-writable locations and for shared interpreters such as /usr/bin/python3,
which would over-grant.
Gateway (Server)
| Command | Description |
|---|---|
kirocrew gateway |
Start dashboard + Slack gateway |
kirocrew gateway --slack-only |
Slack only — skip dashboard web server |
kirocrew gateway --no-crons |
Skip cron scheduler |
kirocrew gateway --port 9999 |
Override dashboard port |
kirocrew gateway --port auto |
OS-assigned ephemeral port |
kirocrew gateway --no-open |
Don't auto-open dashboard URL in browser |
kirocrew gateway --approval reads |
Auto-approve read-only tools |
kirocrew gateway --approval yolo |
Auto-approve all tools (requires isolated KIROCREW_HOME) |
kirocrew gateway --approval interactive |
Prompt for every tool (default) |
kirocrew gateway --seed FIXTURE |
Seed $KIROCREW_HOME from fixture before starting (dev) |
kirocrew gateway --seed-replace |
Wipe a non-empty target home and re-seed it (paired with --seed) |
kirocrew gateway --no-tunnel |
Never publish a tunnel for this process's whole life, whatever tunnel.enabled says. Scoped to TUNNELS: it does not change where the dashboard binds |
kirocrew gateway --json-ready |
Print one KIROCREW_READY:{...} line (port, token, pid, KIROCREW_HOME) once the dashboard is bound |
kirocrew gateway --test-mode |
Alias for --port auto --no-open --json-ready --approval reads |
kirocrew stop |
Stop a running gateway |
kirocrew stop --port 9999 |
Stop gateway on specific port |
kirocrew restart |
Restart gateway (service-aware) |
kirocrew status |
Show runtime stats (uptime, sessions, crons, lessons) |
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.
- today Changed · +79 lines cd32c74f46ff
- 8d ago First seen · 463 lines · 36 tokens per session scan B 40916fab131b
kirocrew-commands is a skill published in the GitHub repository kirodotdev/KiroCrew (3,687 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 8,259 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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…
executive-financial-briefing
Generates a concise executive-level financial briefing or summary suitable for a CEO, CFO, or board presentation. Use when the user asks for a summary, briefing, executive summary, board update, financial overview, financial health check, or "how is the business doing". Covers the full P&L picture in one page. Also…
multi-quarter-trend-analysis
Analyzes financial trends across multiple quarters by comparing P&L metrics over time. Use when the user wants to see trends, patterns, trajectories, or directional movement across 3 or more quarters. Also use for "how are we trending", "show me the trend", "track performance over time", "quarter over quarter…
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.
persistent-notes
Save notes locally to /mnt/workspace/notes.json file. Use when user wants to "save a note" or "remember something".