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 dashboardgit 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/dashboard)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/dashboard"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/dashboard/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/dashboard"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.03138 |
| Opus 5.5 | $0.00026 | $0.01255 |
| Sonnet 5.5 | $0.00013 | $0.00628 |
| Haiku 4.5 | $0.00007 | $0.00314 |
Grade A, and why
dashboard 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 yesterday.
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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Dashboard Tab
ONE page per crewmate. You write it, the person owns it, and the gateway keeps it fed.
Three parts, and knowing which is which is most of the job:
| Part | Who | Rule |
|---|---|---|
| the page | you write the HTML | changes only when you apply it, and only you can |
| the values | the crew log folds | pushed in as they move, never typed by you |
| the frame | the gateway | no network, text-only bindings, nothing you write runs outside it |
1. You own it, and nothing lands unapproved
A page goes live through four steps, and only you can run them:
stage -> preview -> a person approves -> apply
- Stage. A save writes the package as a STAGED copy.
view.htmlcarries your markup, your CSS and your script.modelnames every field you bind, and it is also the list the controller pushes, so a binding the model does not declare is refused at the save and told to you by name. Staging records the page and nothing else: it does not go live, it cuts no version, and the controller pushes it no values. - Preview. Show the staged page to the person who will decide on it. A preview records nothing, which is what makes "show me" free when the answer is no.
- A person approves the page they have just read. Ask one sentence they can answer. A page nobody agreed to is a page they undo instead of keep.
- Apply. This cuts a version from the STAGED page and takes no page
argument, so what lands is provably the page they looked at. Then say what
changed, not what the page shows -- they are looking at the contents.
The person may also press Keep or Discard on the preview themselves, so
re-read your
[DASHBOARD]block before callingdashboard_apply.
dashboard_save is the tool that stages an authored page, and it ships in
#18851. Until it is in your
hands, saving the package only BINDS the page: the tab keeps drawing the
template instance, no version is cut, and your agentic field writes to that
crewmate are refused package_display_pending until a person cuts one. So the
page you saved is not yet the page they see. Describe it, get their yes, and
leave the cut to them.
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.
- yesterday Changed · +136 lines · +1 tokens per session 9988f0065089
- 2d ago Changed · +25 lines 11f36a39c3e9
- 3d ago Changed · +11 lines 5399973c254d
- 4d ago Changed · +4 lines 86050607fc6b
- 8d ago First seen · 73 lines · 65 tokens per session scan A b2aaa36e97a2
dashboard is a skill published in the GitHub repository kirodotdev/KiroCrew (4,449 stars, last pushed today), licensed Apache-2.0. It adds 66 tokens to every session and 3,138 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-10-08.
Other skills, from other repositories
pto-planning
Check an employee's PTO balance and policy, then plan or submit a time-off request.
bootstrap
Onboarding conversation to generate a user profile.
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.
ecosystem-defrag
Inventory an existing Windows agent/developer-tool setup, identify concrete capability overlap, and plan or execute a reversible consolidation when the setup is fragmented.
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…
sector-rotation
Identify which market sectors to overweight or underweight based on current macro conditions and sector performance data.