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-replangit 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-replan)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/mochi-replan"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/mochi-replan/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/mochi-replan"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/mochi-replan.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.00027 | $0.00806 |
| Opus 5 | $0.00014 | $0.00403 |
| Sonnet 5 | $0.00005 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
mochi-replan 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@mochi-replan — Partial Queue Adjustment
Adjust the current plan without starting from scratch. Faster and cheaper than @mochi-plan.
Context to Read
get_plan()— current queue (pending tasks only, done tasks filtered out)get_watchlist()— active watch items (check for overdue items that need scheduling)read_mochi_file({ which: "activity" })— recent activity (last 5-10 entries)- The
planner_notesfrom the queue — contains memory from the last full plan
Do NOT re-read the calendar. That is only for mochi-plan.
Two Modes
Automatic Mode (triggered by poller when needs_replan is true)
Detect what changed and adjust:
-
User dragged the pet (activity shows drag/interrupted_by_user): → Remove the next scheduled move task → Add a playful reaction:
{ type: "notify", action: { summary: "Hey! I was going somewhere!" }, category: "reaction" }→ Optionally add a new move back to a natural position -
User sent a message referencing the plan (activity shows recent chat): → Check if any queued tasks conflict with what the user said → Adjust accordingly
-
Watched item status changed: → If a watch result notification came in (activity log), update planner_notes.watching_last_status → Note: watch checks are driven by WatchlistService, not the queue. Do NOT schedule check_watching tasks.
-
General drift (time passed, some tasks executed): → Rebalance remaining tasks if timing feels off
Explicit Mode (triggered by chat agent with user request)
The chat agent will provide context about what the user wants. Common requests:
- "Remind me at 5pm" → Chat agent handles this directly via
update_watchlist+update_plan(see prompt.md Watch List section). Replan is only needed if the chat agent setsneeds_replan: true. - "Watch this page" → Chat agent handles this directly via
update_watchlist. WatchlistService timer will handle periodic checks automatically based onnextCheckAfter. - "Be quiet for a while" → Remove upcoming notify tasks, keep only moves
- "Come here" → This should use
perform_pet_actioninstead (instant), but if it comes through replan, add an immediate move - "Stop moving" → Remove upcoming move tasks
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 First seen · 72 lines · 27 tokens per session scan A a27abfb99247
mochi-replan is a skill published in the GitHub repository kirodotdev/KiroCrew (3,703 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 806 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
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…
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".