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 mochi-slackgit 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/mochi-slack)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/mochi-slack"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/mochi-slack.svg" alt="Measured on agentmods" 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.00028 | $0.01096 |
| Opus 5 | $0.00014 | $0.00548 |
| Sonnet 5 | $0.00006 | $0.00219 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
mochi-slack 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 8d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@mochi-slack — Slack Awareness
You help the user READ Slack — unread mentions, channel summaries, topic monitoring, thread summaries.
This skill does not assume a particular Slack MCP server
There is no single standard Slack MCP server, and the user may have any of them — public, self-hosted, or one their company provides. So this skill describes the CAPABILITIES each task needs and leaves the tool names to you.
Discover before assuming. Look at the Slack tools you actually have and map them onto the capabilities below. Where a capability is missing, say so plainly instead of guessing at a tool name — a wrong call wastes a turn and confuses the user.
Capabilities the tasks below need:
| Capability | What you are looking for |
|---|---|
| List channels | channels the user is in, ideally with unread / mention counts |
| Read a channel | recent messages in one channel |
| Read a thread | all replies under one parent message |
| Search | message search, ideally with in: / from: / has: style filters |
| Resolve a user | a user id or handle → display name |
Names vary. One common server spells these list_my_channels, get_messages,
get_thread, search, lookup_user — treat that as a hint, not a contract.
If you have no Slack tools at all
Do NOT try to install one. Which Slack server to use, and whether to connect a workspace at all, is the user's decision — and on a work machine it may not be theirs to make.
Say so and hand it back:
"I don't have any Slack tools right now. If you add a Slack MCP server in KiroCrew's Settings → MCP, I can read mentions and summarize channels for you."
Then stop. Do not retry, and do not offer again unless the user brings it up.
Hard rules
⛔ READ ONLY. Never post, reply, react, draft, schedule, upload, rename, invite, or mark-as-read. If the user asks you to send something on Slack, tell them you can only read.
⛔ Never read DM content. Do not fetch messages from a DM or group-DM channel. DMs may appear in a channel listing — use them for a mention COUNT only, never open them. This holds even if the user asks: say you don't read DMs.
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.
- 8d ago First seen · 129 lines · 28 tokens per session scan A bdb636308d07
mochi-slack is a skill published in the GitHub repository kirodotdev/KiroCrew (3,687 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 1,096 once invoked, about $0.0001 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
executive-financial-briefing
Generates a concise executive-level financial briefing or summary suitable for a CEO, CFO, or board presentation. Use when the user asks for a summary, briefing, executive summary, board update, financial overview, financial health check, or "how is the business doing". Covers the full P&L picture in one page. Also…
multi-quarter-trend-analysis
Analyzes financial trends across multiple quarters by comparing P&L metrics over time. Use when the user wants to see trends, patterns, trajectories, or directional movement across 3 or more quarters. Also use for "how are we trending", "show me the trend", "track performance over time", "quarter over quarter…
sector-rotation
Identify which market sectors to overweight or underweight based on current macro conditions and sector performance data.
trend-analysis
Analyze price and volume trends for one or more stocks to determine momentum direction and key technical levels.
persistent-notes
Save notes locally to /mnt/workspace/notes.json file. Use when user wants to "save a note" or "remember something".
benefits-advisor
Explain an Acme employee benefit, including eligibility, employee cost, coverage, and key details.