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 agentmods add skills/kirodotdev/kirocrew/meetingsnpx 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.svg" alt="Measured on agentmods" 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 | $0.00072 | $0.01002 |
| Opus 5 | $0.00036 | $0.00501 |
| Sonnet 5 | $0.00014 | $0.00200 |
| Haiku 4.5 | $0.00007 | $0.00100 |
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 — 88 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. Each agent owns exactly ONE output file and rewrites it in full after every batch.
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) |
<id> is the meeting id with : replaced by _. Only [A-Za-z0-9._-] is
legal in it — the backend rejects anything else, so do not construct a path from
a raw calendar UID.
Lifecycle
idle— the meeting folder exists, nothing is running.active— transcription is flowing; agents receive batched lines every ~30s.paused— transcription stopped, the session and its queues are intact.reviewing— the meeting is over and the user is triaging extracted tasks.ended— finished; outputs are final.
The agents
| Agent | Writes | Notes |
|---|---|---|
meetings-note-taker |
note-taker.md |
structured notes: topics, decisions, action items, open questions |
meetings-sketch-artist |
sketch-artist.html |
one self-contained HTML/Mermaid diagram, revised in place |
meetings-task-extractor |
tasks.json |
always runs; the app's core output |
Each agent's first message carries an OUTPUT_FILE: line. Write to that exact
path, character for character, and rewrite the FULL file after every batch —
never accumulate content in memory, because a context limit would lose 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.
- 5d ago First seen · 88 lines · 72 tokens per session scan A 2b89ce843aa7
meetings is a skill published in the GitHub repository kirodotdev/KiroCrew (3,532 stars, last pushed 2d ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,002 once invoked, about $0.0004 per session on Opus 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
kodama-verification
Define measurable success criteria and collect targeted test, build, lint, type-check, or smoke-test evidence before claiming work is complete.
kodama-behavior
Classify requests, assess unfamiliar codebases, delegate work safely, and recover from failed attempts. Use for multi-step, ambiguous, or parallelizable work.
kodama-constraints
Enforce non-negotiable safety, scope, security, and quality constraints for implementation and review work.
project-release-check
Validate this example project's release readiness. Use before publishing a release candidate.
aatmf-t10-confidentiality-breach
AATMF T10 — Integrity & Confidentiality Breach. System prompt extraction, training-data extraction, model-weight leakage, private-key recovery.
sidewinder-rattlesnake
Adversary-emulation profile for SideWinder (G0121 / Rattlesnake / T-APT-04 / Razor Tiger), India's suspected state-sponsored cyber-espionage actor.