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 web-browsegit 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/web-browse)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/web-browse"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/web-browse/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/web-browse"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/web-browse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.02454 |
| Opus 5.5 | $0.00026 | $0.00982 |
| Sonnet 5.5 | $0.00013 | $0.00491 |
| Haiku 4.5 | $0.00007 | $0.00245 |
Grade A, and why
web-browse 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 9d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Browse: open a real page for the user to look at
Your PRIMARY way to open a page in the dashboard's Browser panel is the
browser MCP tool — it drives the built-in Electron panel in-process, with
no separate Chromium and no macOS security prompt:
browser(op="navigate", args={"url": "https://example.com"})
Other ops: snapshot (get element refs), then click / type / press_key /
hover / select_option / screenshot / wait_for / back / console. Call
snapshot first to get refs before a click/type.
The tool opens PUBLIC http(s) URLs, plus loopback origins the operator
listed. A loopback, .localhost, private, link-local, CGNAT or metadata
address is refused, with an error pointing at playwright-cli open <url> — the
path that prompts for the approval such a target requires. The one exception is
an exact host:port (localhost, 127.0.0.1 or [::1] plus a port) the
operator listed in the dashboard's local-origins setting; the gateway's own port is
refused even when listed, and you cannot edit that list. So a local dev server
is the playwright-cli path (see the web-verify and web-preview
skills) unless the operator told you its origin is listed: then navigate opens
it in the panel, and a refusal means it is not listed, so fall back to
playwright-cli.
If the tool returns guidance that no native panel is serving this session (a
remote gateway, or a plain-browser dashboard with no Electron panel), THEN fall
back to playwright-cli (below). Do not reach for playwright-cli first: on the
desktop app it spawns its own unsigned Chromium and triggers a macOS security
prompt, and the user is watching the built-in panel, not that window.
Fallback (and attach / logged-in sessions): playwright-cli
The dashboard's right-side Browser panel also shows a live playwright-cli
session. When the browser tool reports no native panel, open a page with:
playwright-cli open https://example.com
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.
- 9d ago Changed · +8 lines 8b3608fb6095
- 10d ago Changed · +6 lines 2f72a4867c15
- 20d ago Changed · +6 lines e8bffc480a36
- 28d ago Changed · +6 lines 4fcb23e8d0b9
- 1mo ago Changed · -27 tokens per session a961e16f8dd8
- 1mo ago Changed · -54 lines a17aed0780b9
- 1mo ago Changed · +3 lines 5aac9e044b18
- 1mo ago Changed · +25 lines 048e88c4a166
- 1mo ago First seen · 195 lines · 93 tokens per session scan A 4b1ab364fea4
web-browse is a skill published in the GitHub repository kirodotdev/KiroCrew (4,534 stars, last pushed today), licensed Apache-2.0. It adds 66 tokens to every session and 2,454 once invoked, about $0.0003 per session on Opus 5.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
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.
creating-actions
This skill should be used when the user asks to "create an action", "save this flow as an action", "make this replayable", "record a reusable action", "author a Maestro flow as an action", "add a login/setup action", or when a verified UI walk should be persisted under .rn-agent/actions/ so future sessions can replay…
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol.
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…
trend-analysis
Analyze price and volume trends for one or more stocks to determine momentum direction and key technical levels.
sector-rotation
Identify which market sectors to overweight or underweight based on current macro conditions and sector performance data.