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 meetingsgit 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/meetings)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/meetings"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/meetings/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/meetings"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/meetings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Rogue Agent · line 17 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.00062 | $0.01644 |
| Opus 5.5 | $0.00025 | $0.00658 |
| Sonnet 5.5 | $0.00012 | $0.00329 |
| Haiku 4.5 | $0.00006 | $0.00164 |
Grade A, and why
meetings 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 5d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meetings app
The Meetings app transcribes a live meeting and fans each line out to a small
crew of background agents. A file-backed agent (widget_type markdown or
html) owns exactly ONE output file and rewrites it in full after every batch.
An agent whose widget_type is chat has no output file — its output IS its
chat replies, it gets no OUTPUT_FILE line, and none of the file rules below
apply to it.
Only a markdown agent's output is user-editable in the app (the editable
minutes). A user edit never touches the agent's file: it is saved as a separate
sidecar under edits/ that the dashboard shows in place of the agent's output,
so the agent's next rewrite cannot destroy it. That edits/ tree is a sensitive
path — no agent can read or write it through file tools — so the agent's own
file is NOT what the user sees once they have edited it. An html output is not
user-editable.
Only one meeting may be active at a time; starting a second answers 409. The
server enforces the lifecycle transition table, not just the UI: active and
paused may only reach ended through reviewing (the action-item review
gate) on the status route, reviewing may go back to paused, ended may be
reopened to active, and a same-status POST is an idempotent no-op. Stop
(POST …/meetings/<id>/stop) is the separate exit that ends a meeting outright.
A live translation panel translates each transcript line as it lands, using one
tool-less kirocrew-lite call per line in an ephemeral session — deliberately
NOT the agent batch path, because latency is the point. It is sequential per
meeting and drops the oldest pending line when it falls behind, so gaps in
translations.json are expected, not a bug.
Where the data lives
All paths are under ~/.kiro/crew/apps/meetings/data/:
| Path | What it is |
|---|---|
config.json |
app config: the agent roster, the task/calendar provider ids, presets |
dictionary.toml |
speech-to-text correction terms ([[term]] blocks) |
calendar-cache.json |
the last calendar sync's events |
task-ledger.json |
tasks filed through the local task provider |
meetings/<id>/session.json |
one meeting's metadata (title, status, attendees, attachments, outputs map) |
meetings/<id>/tasks.json |
that meeting's extracted action items |
meetings/<id>/<agent-id>.md |
a markdown agent's output (e.g. note-taker.md) |
meetings/<id>/<agent-id>.html |
an HTML agent's output (e.g. sketch-artist.html) |
meetings/<id>/transcript.jsonl |
the raw transcript, one finalized speech segment per line — read this instead of asking the user to re-summarize |
meetings/<id>/translations.json |
per-line translations for the live translation panel |
edits/<id>/<agent-id>.md |
the user's edit of a markdown output — not readable by agents (see above) |
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.
- 5d ago Changed c759e2fd908b
- 11d ago Changed · +8 lines 117941ea8bb8
- 18d ago Changed · +1 lines d985ecf16d47
- 29d ago Changed · -10 tokens per session a2b820840444
- 1mo ago Changed · +23 lines 431bade183e0
- 1mo ago Changed · +6 lines bd94d697bad3
- 1mo ago First seen · 88 lines · 72 tokens per session scan A 2b89ce843aa7
meetings is a skill published in the GitHub repository kirodotdev/KiroCrew (4,481 stars, last pushed today), licensed Apache-2.0. It adds 62 tokens to every session and 1,644 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.
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.