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 Kripu77/software-factory --skill loop-on-cigit clone --depth 1 https://github.com/Kripu77/software-factoryWrote 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/kripu77/software-factory/loop-on-ci)<a href="https://agentmods.dev/skills/kripu77/software-factory/loop-on-ci"><img src="https://agentmods.dev/badge/skills/kripu77/software-factory/loop-on-ci/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/kripu77/software-factory/loop-on-ci"><img src="https://agentmods.dev/badge/skills/kripu77/software-factory/loop-on-ci.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.00028 | $0.00401 |
| Opus 5.5 | $0.00011 | $0.00160 |
| Sonnet 5.5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
loop-on-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 1mo 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.
What it actually says
Loop on CI
Trigger
Need to watch a branch or pull request and iterate on CI failures until all required checks are green.
Use gh pr checks as the source of truth. It includes all PR-attached checks, while gh run list only covers GitHub Actions.
Workflow
-
Resolve the PR for the current branch.
-
Inspect current PR checks before waiting.
-
If checks already failed, diagnose those failures first.
-
If checks are pending, watch with
gh pr checks --watch --fail-fast. -
After each push, re-check the full PR check set and repeat until green.
Commands
# Resolve the active PR
gh pr view --json number,url,headRefName
# Inspect all attached checks
gh pr checks --json name,bucket,state,workflow,link
# Watch pending checks and fail fast
gh pr checks --watch --fail-fast
# GitHub Actions logs, when the failing check links to a GHA run
gh run view <run-id> --log-failed
Guardrails
-
Keep each fix scoped to a single failure cause when possible.
-
Do not bypass hooks (
--no-verify) to force progress. -
If the failure is clearly unrelated to the PR and appears fixed on main, merge latest main instead of bloating the PR with unrelated fixes.
-
If failures are flaky, retry once and report flake evidence.
-
Re-run
gh pr checks --json name,bucket,state,workflow,linkafter every push; the check set can change.
Output
-
Current CI status
-
Failure summary and fixes applied
-
PR URL once checks are green
Factory override
Never merge. Never gh pr merge. Only the dispatched PR.
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.
- 1mo ago First seen · 65 lines · 28 tokens per session scan A 38e956e1cc62
loop-on-ci is a skill published in the GitHub repository Kripu77/software-factory (7 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 401 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
devops-assistant
Assists in version control, deployment, and automation tasks, ensuring smooth DevOps operations and workflow efficiency.
check-dependabot
Validate a Dependabot configuration against the published JSON Schema and audit its groups against the repository's real dependency manifests. Use when creating or rewriting .github/dependabot.yml, when adding or reorganising groups, ignore or exclude-patterns, when a dependency lands in the wrong grouped PR or keeps…
monitor-ci
Drive a long-running GitHub Actions run to a trustworthy conclusion without burning the session on polling. Use when asked to wait for a pipeline, watch a build, babysit a release or deploy run, restart it if it fails, or report whether it went green. Also use when a run must finish before a follow-up step such as a…
abd-devops
ABD DevOps agent: scaffolds CI/CD, validates .env.example coverage, checks Dockerfile hygiene, and handles release tasks.