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 cron-cost-optimizegit 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/cron-cost-optimize)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/cron-cost-optimize"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/cron-cost-optimize/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/cron-cost-optimize"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/cron-cost-optimize.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.00073 | $0.02310 |
| Opus 5.5 | $0.00029 | $0.00924 |
| Sonnet 5.5 | $0.00015 | $0.00462 |
| Haiku 4.5 | $0.00007 | $0.00231 |
Grade A, and why
cron-cost-optimize 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimize what registered cron jobs cost
A cron job that dispatches to the model pays for its whole injected context on every wake, whether or not that wake had anything to do. Two cheaper modes exist and neither reaches a job that was already registered without them.
| Mode | What it costs | What it gives up |
|---|---|---|
script or command job |
no model turn at all | all reasoning, and the carried previous result |
agent job with minimal_context |
a model turn on a small context | memory, lessons, steering, skills, prior session history |
| plain agent job | a model turn on the full context | nothing |
Your job in this skill is to move each of the user's jobs to the cheapest mode it can safely use, and to leave alone the ones that genuinely reason.
Run the scan first
The scan is deterministic, so it costs no inference. Run it before forming any opinion.
It reads nothing from disk. Two steps, and the first one matters:
- Call
cron_listwithjsonset to true. That is the only reader that can see what the scan needs. The job store is scoped to the jobs your session owns, and the run history is readable only by the gateway, so a script cannot fetch either itself. - Write that JSON to a file and pass it in. Do NOT put the document on the command
line -- a prompt inside it containing backticks or
$(...)would be executed by the shell.
python3 <this skill's dir>/scripts/cron_cost_scan.py --input <the file you wrote>
Resolve <this skill's dir> from wherever you loaded this SKILL.md, rather than
hardcoding a path. The data home moves with KIROCREW_HOME, so a hardcoded
~/.kiro/crew/skills/... is wrong for some users.
Useful flags:
--jsonfor machine-readable output when you need to fold the result into a table.--min-runs Nto change how many recorded runs count as evidence. Default is 5.
To look at one job, narrow the cron_list call with its ids instead of filtering
afterwards.
cron_list answers a plain sentence rather than JSON in three real cases: an empty
registry, no jobs owned by this session, and a caller the gateway cannot identify.
The script says which one it got. Relay it as-is; none of the three is an error.
What ships with it
1 file 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 693ab3cb25ba
- 8d ago Changed · +4 lines b37e60b9aae2
- 26d ago Changed · -29 tokens per session ff33bf8169fe
- 1mo ago First seen · 175 lines · 102 tokens per session scan A 7b94bbcdc398
cron-cost-optimize is a skill published in the GitHub repository kirodotdev/KiroCrew (4,449 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 2,310 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-09-10.
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…
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.
deploying-to-staging-environment
Use when deploying changes to staging across relay, relay-dashboard, and relay-cloud repos - coordinates multi-repo branch syncing using git worktrees, automatically triggers staging deployments via GitHub Actions.
writing-relayflows
Use when authoring a Relayflows flow (@relayflows/surface / @relayflows/sdk, the journal-based v2 engine — the CLI is flows, package versions 2.0.x) in TypeScript or YAML/JSON. Covers the three-rung ladder (run/llm/agent), the resident verbs (human/dispatch/done), verification gates, TypeScript vs YAML authoring…
browser-testing-with-screenshots
Use when testing web applications with visual verification - automates Chrome browser interactions, element selection, and screenshot capture for confirming UI functionality.