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.svg" alt="Measured on agentmods" 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.00142 | $0.13905 |
| Opus 5 | $0.00071 | $0.06953 |
| Sonnet 5 | $0.00028 | $0.02781 |
| Haiku 4.5 | $0.00014 | $0.01391 |
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 today.
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 — 904 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.
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/claim_preflight.py— one verdict per candidate item before you dispatch it:CLAIM/SKIP/CLOSE/REVIEW/UNKNOWN.scripts/fleet_probe.py— batch worker-tail classification + idle age + error tails + banned-process scan + host load + delivery counters, in ONE call per cycle.scripts/credit_spend.py— per-item credit rollup + budget verdict.
A decision this procedure states as prose rots silently; a decision a script computes can be tested. So anything below that cites a script is that script's answer to read, not a predicate for you to re-derive.
The pipeline spec
The operator's seed message names a spec file (JSON). Fields you consume now:
{
"id": "issue-fix",
"repo": "<owner>/<repo>",
"default_branch": "main",
"work_source": {"kind": "gh_issues", "select_labels": ["auto-fixable"],
"skip_signals": ["claimed", "in-progress"]},
"worker_contract": {"branch_pattern": "fix/{slug}-{n}",
"worktree_pattern": "../{repo_name}-fix-{n}"},
"governance": {"max_in_flight": 32, "max_per_cycle": 3,
"idle_alert_secs": 900, "session_ceiling": 30,
"credit_budget_per_item": 100, "topup_ceiling": 2},
"interface": {"folder_name": "pipeline-{id}", "digest_language": "auto"}
}
Anything the spec does not set has the default shown above. Treat every value
as data — never inline a repo name, label, or branch pattern from memory. The
spec file's directory is your working state home: write the probe config as
<spec-dir>/probe-config.json and let the probe own
<spec-dir>/probe-config.json.state.json (the handled-set). Set
fleet_worktrees to the absolute worktree roots this fleet owns: it is optional
in the config and it is what makes cwd=fleet reachable, so leaving it out
classifies every banned line as foreign or unknown and the enforcing row of
the banned-ops table never fires.
What ships with it
3 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.
- today Changed · +39 lines a9dde0b6bce4
- yesterday Changed · +14 lines f10582279d23
- 2d ago Changed · +568 lines · +21 tokens per session 6768a386e29d
- 5d ago First seen · 283 lines · 121 tokens per session scan A c0db557bb61d
pipeline-conductor is a skill published in the GitHub repository kirodotdev/KiroCrew (3,687 stars, last pushed today), licensed Apache-2.0. It adds 142 tokens to every session and 13,905 once invoked, about $0.0007 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-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.