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 computer-usegit 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/computer-use)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/computer-use"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/computer-use/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/computer-use"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/computer-use.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.00062 | $0.06697 |
| Opus 5.5 | $0.00025 | $0.02679 |
| Sonnet 5.5 | $0.00012 | $0.01339 |
| Haiku 4.5 | $0.00006 | $0.00670 |
Grade A, and why
computer-use 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 — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Computer Use — driving native desktop apps
You have MCP tools that read and operate the user's real applications through
the operating system's accessibility layer. This is not a browser: use it when the
work lives in a desktop app (a spreadsheet, a PDF viewer, a native internal tool,
a dialog box), and use playwright-cli (the web-browse skill) for web pages.
Two things to internalise before your first call:
- Address elements by index, from a snapshot you were just shown. That is the path to prefer for everything: it activates the control directly, it is checked against drift, and the mouse pointer does not move. Coordinates exist as a fallback for canvases, maps and custom-drawn UI that expose no element — see Coordinates and dragging.
- It is off unless the user turned it on (Settings → Computer Use). The full tool set runs on macOS and Windows alike. They differ in ONE way worth relaying: Windows has no per-process input, so a keystroke takes the user's keyboard focus and a coordinate click moves their real cursor. A "disabled" or "not supported" refusal is a real configuration answer, not a transient error — relay it and stop; do not retry.
The loop
1. Find the app.
computer_list_apps()
Returns the on-screen applications with their bundle ids, pids and window titles.
Skip this if the user named an app you can pass straight through — app accepts a
display name ("Finder", "Preview") or a bundle id
("com.apple.finder"), matched case-insensitively.
If the app you need is not running, open it:
computer_launch_app(app="Paint")
Give the app's NAME as the OS knows it — the name in the Start menu or the Applications folder. A filesystem path, a command line and a document are all refused, because this opens an application and nothing else; if you find yourself wanting to pass a path, the answer is to launch the app and then use the tools below to open the file from inside it.
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 · +2 lines 863b2629177f
- 27d ago Changed · -43 tokens per session 8c8c019849f3
- 1mo ago Changed · -25 lines 99348f950f4d
- 1mo ago Changed · +4 lines 83e51691c7a9
- 1mo ago First seen · 464 lines · 105 tokens per session scan A 9db7e0415afe
computer-use is a skill published in the GitHub repository kirodotdev/KiroCrew (4,464 stars, last pushed today), licensed Apache-2.0. It adds 62 tokens to every session and 6,697 once invoked, about $0.0002 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
pto-planning
Check an employee's PTO balance and policy, then plan or submit a time-off request.
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…
bootstrap
Onboarding conversation to generate a user profile.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol.
workflow-helper
Guidance for creating, managing and executing workflow automations that chain multiple tools and agents together. Use when the user asks about building, listing, running or composing workflows and automated task pipelines.