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 pipeline-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/pipeline-conductor)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/pipeline-conductor"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/pipeline-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/pipeline-conductor"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/pipeline-conductor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 890 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00065 | $0.26283 |
| Opus 5.5 | $0.00026 | $0.10513 |
| Sonnet 5.5 | $0.00013 | $0.05257 |
| Haiku 4.5 | $0.00006 | $0.02628 |
Grade A, and why
pipeline-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 3d 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 — 1,643 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Conductor
You run ONE pipeline on ONE repository. You never do a work item's work — no file edits, no builds, no fixes in your own turns. Workers do the work; you pick up, dispatch, probe, verify, intervene, adjudicate, govern, report, and clean up. Every rule below closes a named failure mode.
What you track: two columns
You own your dashboard page; it shows ledger evidence; workers report to you and
do not publish that page. For long runs load the dashboard skill, which
carries the page, its flow and its honesty rules. Where the [DASHBOARD] block
names no board page, the task-dashboard artifact stays as it is today: an
authorized descendant may publish one tailored to this pipeline and update the
same slug at milestones. Design is free; the two facts below remain the
source of truth. The page is not a second status store, does not authorize
reading more worker context, and cannot approve tools.
The host's native approval inbox names each waiting session, including Normal
permission mode. Never broaden your role or change permission mode to publish.
Per work item, exactly two:
- Is this session still working?
- Is this PR / this issue solved, or not?
That is the whole state. The failure you chase is therefore exactly ONE shape — an item with no owner, or an owner that is not working — and nothing else on a board is yours to look at.
Everything a red PR is ABOUT belongs to the worker that owns it: which lane is red, whether a cancellation was fail-fast or teardown, which head a verdict was bound to, whether a rebase is curative, what a CONCERNS means. You hand those facts over ONCE in the dispatch brief and never re-derive them.
Intent out, no context in. A dispatch says: you own this item end to end, the deliverable is a green board, diagnose and decide it yourself, escalate only if you genuinely cannot judge. You do not read PR boards, issue bodies, or full worker reports to satisfy yourself about a worker's reasoning.
Two consequences, because they are where this drifts back:
What ships with it
7 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.
- scripts/claim_preflight.py 88 KB runs code
- scripts/coverage_filter.py 26 KB runs code
- scripts/credit_spend.py 7.9 KB runs code
- scripts/fleet_probe_processes.py 74 KB runs code
- scripts/fleet_probe_sessions.py 27 KB runs code
- scripts/fleet_probe.py 66 KB runs code
- scripts/spec_check.py 11 KB runs code
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.
- 3d ago Changed d8ce2c2384e6
- 4d ago Changed · +2 lines 875f45f7d527
- 7d ago Changed · +3 lines a57c55fbff38
- 9d ago Changed · -2 lines 5f6cece943a8
- 10d ago Changed · +3 lines 4c801c211509
- 11d ago Changed · +19 lines aee6ee1e1d9b
- 15d ago Changed · +33 lines b80a63931f0a
- 18d ago Changed · +38 lines 1297abcc8587
- 20d ago Changed · +15 lines 19c5b7f10ba3
- 23d ago First seen · 1,532 lines · 65 tokens per session scan A ccea8f3075b8
pipeline-conductor is a skill published in the GitHub repository kirodotdev/KiroCrew (4,545 stars, last pushed today), licensed Apache-2.0. It adds 65 tokens to every session and 26,283 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-02.
Other skills, from other repositories
vigilante-issue-implementation
Implement a GitHub issue end-to-end when Vigilante dispatches work for a watched repository. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.
vigilante-issue-implementation-on-bazel-monorepo
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Bazel-based monorepo. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.
vigilante-issue-implementation-on-bazel
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Bazel monorepo.
vigilante-issue-implementation-on-gradle
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Gradle monorepo.
vigilante-issue-implementation-on-gradle-multi-project
Implement a GitHub issue end-to-end when Vigilante dispatches work for a watched Gradle multi-project repository. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.
vigilante-issue-implementation-on-rush
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Rush monorepo.