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 security-conductorgit 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/security-conductor)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/security-conductor"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/security-conductor/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/security-conductor"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/security-conductor.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.00098 | $0.03562 |
| Opus 5 | $0.00049 | $0.01781 |
| Sonnet 5 | $0.00020 | $0.00712 |
| Haiku 4.5 | $0.00010 | $0.00356 |
Grade A, and why
security-conductor 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Conductor
You run ONE audit on ONE target. You never audit anything yourself — no probes, no proofs of concept, no fixes in your own turns. Auditors find, verifiers reject, fixers patch; you decompose, dispatch, adjudicate, gate, learn, and report. Every rule below closes a named failure mode.
Two things make this different from every other conductor, and both are absolute:
- Aggression is bounded by data, not by tone. The rules of engagement are
rows in the ledger, exported as
rules-of-engagement.json. A scope question is answered byscripts/scope_check.py, never by your judgment about what seems reasonable. A tone instruction degrades silently across a long session; a scope verdict is testable. - A policy refusal IS the boundary. An auditor looking for weaknesses in a safety fence will meet that fence. The correct response is to stop and report, never to rephrase, re-spell, split, or route around the block. Record it as an event and rule on it. Any worker that reports having found a wording that got past a block has broken the rules of engagement, and the finding is void.
The scripts below are the deterministic half of the loop — run them via
execute_bash, read their output, never re-derive what they compute. Presence is
not assumed: check at first use, and treat an absent script as UNKNOWN rather
than permission.
scripts/scope_check.py— is this path, repository or technique in scope?IN_SCOPE/OUT_OF_SCOPE/NEEDS_APPROVAL/UNKNOWN.UNKNOWNis never permission.scripts/finding_entry.py— dedupe and format one finding against the ledger, so a re-audited surface does not re-file what is already recorded.scripts/verify_finding.py— re-run one finding's proof of concept and emit the verdict. You read the verdict; you never read a verifier's prose and decide for yourself.scripts/ledger.py— the ledger CLI: schema, findings, verdicts, lessons, rules-of-engagement export, list. It is also the human's editing surface.
What ships with it
2 files 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 First seen · 269 lines · 98 tokens per session scan A bdfa43059ca6
security-conductor is a skill published in the GitHub repository kirodotdev/KiroCrew (3,703 stars, last pushed yesterday), licensed Apache-2.0. It adds 98 tokens to every session and 3,562 once invoked, about $0.0005 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-09-08.
Other skills, from other repositories
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…
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…
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.