Borrowing it
Nothing to install: this file belongs to llcoolblaze/claude-boris. 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/llcoolblaze/claude-boris/main/.claude/commands/ci-loop.mdgit clone --depth 1 https://github.com/llcoolblaze/claude-borisWrote 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/llcoolblaze/claude-boris/ci-loop)<a href="https://agentmods.dev/commands/llcoolblaze/claude-boris/ci-loop"><img src="https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/ci-loop/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/llcoolblaze/claude-boris/ci-loop"><img src="https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/ci-loop.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.00024 | $0.01060 |
| Opus 5.5 | $0.00010 | $0.00424 |
| Sonnet 5.5 | $0.00005 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
ci-loop 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Loop
Pre-flight Check
!git status --short
!git branch --show-current
!gh run list --limit 3 2>/dev/null || echo "gh CLI not configured"
CI Loop Protocol
Configuration
- Max Iterations: 5
- Poll Interval: 30 seconds
- Auto-fix: Lint, Types (Tests require confirmation)
1. Initial Push
BRANCH=$(git branch --show-current)
echo "🚀 Pushing to $BRANCH..."
git push origin "$BRANCH"
2. Wait for CI
echo "⏳ Waiting for CI..."
# Get latest run
RUN_ID=$(gh run list --branch "$BRANCH" --limit 1 --json databaseId -q '.[0].databaseId')
# Watch and wait
gh run watch "$RUN_ID" --exit-status
3. Parse Results
If CI fails:
# Get failure logs
gh run view "$RUN_ID" --log-failed > /tmp/ci-failure.log
# Parse for actionable errors
echo "=== TypeScript Errors ==="
grep -E "error TS[0-9]+:" /tmp/ci-failure.log | head -10
echo "=== Test Failures ==="
grep -A 3 "FAIL\|✕" /tmp/ci-failure.log | head -20
echo "=== Lint Errors ==="
grep -E "error\s+" /tmp/ci-failure.log | head -10
echo "=== Build Errors ==="
grep -E "Error:|BUILD FAILED" /tmp/ci-failure.log | head -10
4. Auto-Fix Attempt
Lint Errors (auto-fixable):
npm run lint:fix
Type Errors (analyze and fix):
- Parse error location
- Determine fix
- Apply carefully
Test Failures (requires analysis):
- Understand what failed
- Determine if test or code issue
- Fix accordingly
Build Errors (investigate):
- Usually dependency or config
- May need manual intervention
5. Commit Fixes
git add -A
git commit -m "fix: address CI failures
Auto-fixes applied:
- [List what was fixed]
🤖 CI Loop iteration $ITERATION"
6. Iterate
Repeat steps 1-5 until:
- ✅ All checks pass, or
- ⚠️ Max iterations reached, or
- ❌ Non-auto-fixable issue found
Iteration Tracking
| Iteration | Status | Fixes Applied |
|---|---|---|
| 1 | [Pass/Fail] | [What was fixed] |
| 2 | [Pass/Fail] | [What was fixed] |
| ... | ... | ... |
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 · 202 lines · 24 tokens per session scan A 24e5358137cb
ci-loop is a command published in the GitHub repository llcoolblaze/claude-boris (49 stars, last pushed 9mo ago), licensed MIT. It adds 24 tokens to every session and 1,060 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-30.
Other commands, from other repositories
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.