ci

A command for watching the automated checks on a GitHub pull request and fixing failures on the current branch. It stops before merging.

In plain words
What is it for?
Use it when a pull request needs its continuous-integration checks monitored and any failures corrected before review or merge.
Why use it?
It removes the need to repeatedly check whether tests and other required checks have finished or failed.

Command

Install

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.

agentmods
npx agentmods add commands/kripu77/software-factory/ci
Clone the repo
git clone --depth 1 https://github.com/Kripu77/software-factory
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 197 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.00197
Opus 5 $0.00010 $0.00098
Sonnet 5 $0.00004 $0.00039
Haiku 4.5 $0.00002 $0.00020

Measured 2d ago against content hash 9a5bfe76a97d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ci 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 2d 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.

commands/ci.md · 9 lines

What it actually says

Read lanes/ci.md and AGENTS.md. Run /loop-on-ci on the given PR only. Never --no-verify. Never merge.

At start, factory.sh mem read for this PR. Write started only if none in progress: factory.sh mem write --lane ci --status started --harness <claude|cursor|codex|grok> --pr . At the end, factory.sh mem write --lane ci --status done|blocked|failed --harness <claude|cursor|codex|grok> --pr --summary "" --evidence --next-steps "". That write comments on the GitHub issue or PR. started does not. Missing memory or a comment failure: warn once and continue.

Changes

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.

  1. 2d ago First seen · 9 lines · 19 tokens per session scan A 9a5bfe76a97d

Subscribe to this mod's changes

ci is a command published in the GitHub repository Kripu77/software-factory (7 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 197 once invoked, about $0.0001 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-08-31.

Related

Other commands, from other repositories

fix-issue

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…

yonatangross/orchestkit · 82 tokens

review-pr

PR review using parallel specialized agents for code quality, security, testing, architecture, and performance analysis. Synthesizes findings into a review report with conventional comments (praise/issue/suggestion/nitpick) and approve or request-changes verdict. Use when reviewing pull requests, conducting security…

yonatangross/orchestkit · 69 tokens

expect

Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…

yonatangross/orchestkit · 73 tokens

design-context-extract

Extract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design…

yonatangross/orchestkit · 84 tokens

dev

One-command dev loop boot. Spins up portless (named HTTPS subdomain), emulate (stateful API mocks), the project's dev server, and an agent-browser session, all keyed to the current git branch. Use when starting a feature branch, switching worktrees, or returning to a project after a break. Skips silently with install…

yonatangross/orchestkit · 76 tokens

explore

Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment. Generates ASCII visualizations, import graphs, and design pattern detection with cross-session memory storage. Use when exploring a repo, discovering architecture, onboarding to a…

yonatangross/orchestkit · 68 tokens