Borrowing it
Nothing to install: this file belongs to kaze-jp/kusa. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kaze-jp/kusa/main/.claude/commands/kiro/ao-run.mdgit clone --depth 1 https://github.com/kaze-jp/kusaWrote 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/commands/kaze-jp/kusa/ao-run)<a href="https://agentmods.dev/commands/kaze-jp/kusa/ao-run"><img src="https://agentmods.dev/badge/commands/kaze-jp/kusa/ao-run/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/commands/kaze-jp/kusa/ao-run"><img src="https://agentmods.dev/badge/commands/kaze-jp/kusa/ao-run.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.00000 | $0.00882 |
| Opus 5.5 | $0.00000 | $0.00353 |
| Sonnet 5.5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
ao-run 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 2mo 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AO Autonomous Execution
Launch the Agent Orchestrator for fully autonomous feature development. The orchestrator takes approved specs and drives the entire pipeline: implementation → integration → PR → review → merge.
Usage
/kiro:ao-run <feature-name>
Instructions
-
Validate prerequisites: Verify all required spec documents exist:
.kiro/specs/$FEATURE_NAME/requirements.md(required, R1 approved).kiro/specs/$FEATURE_NAME/design.md(required, R2 approved).kiro/specs/$FEATURE_NAME/tasks.md(required, R3 approved)
If any are missing, report which documents are absent and which commands to run:
/kiro:spec-init→/kiro:spec-requirements→/kiro:spec-design→/kiro:spec-tasks
-
Read configuration from
.ao/ao.yaml:presetandautonomy.downstream— determines how much human intervention is neededgit.strategyandgit.base_branch— worktree vs branch strategyquality_gates.commands— project-specific test/lint/build commandsreviews.*— which review points require human vs AI actors
-
Read steering documents for implementation constraints:
.ao/steering/product.md— product vision and priorities.ao/steering/tech.md— tech stack and coding conventions.ao/steering/structure.md— directory structure and naming rules
-
Launch the orchestrator agent (
orchestrator.md) with the feature name. The orchestrator autonomously executes the full pipeline:Phase 1: Task analysis + worktree branch creation Phase 2: Context generation for implementation workers Phase 3: Parallel implementation (TDD + Team Agents + quality gates) Phase 4: Integration (merge worktrees) + Simplify Phase 5: Ship-Before Checkpoint Phase 6: PR creation + Multi-specialist code review (GH comments) Phase 7: Fix loop (address review feedback until approved) Phase 8: Pre-merge review (human/ai per downstream setting) Merge: Merge to base branch + cleanup
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.
- 2mo ago First seen · 78 lines · 0 tokens per session scan A 05f474cccf77
ao-run is a command published in the GitHub repository kaze-jp/kusa (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 882 tokens. 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.