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 agentmods add commands/ilyasibrahim/claude-agents-coordination/cigit clone --depth 1 https://github.com/ilyasibrahim/claude-agents-coordinationWrote 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/ilyasibrahim/claude-agents-coordination/ci)<a href="https://agentmods.dev/commands/ilyasibrahim/claude-agents-coordination/ci"><img src="https://agentmods.dev/badge/commands/ilyasibrahim/claude-agents-coordination/ci.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.01424 |
| Opus 5 | $0.00008 | $0.00712 |
| Sonnet 5 | $0.00003 | $0.00285 |
| Haiku 4.5 | $0.00002 | $0.00142 |
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 5d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local CI Pipeline
Run comprehensive CI gates locally before pushing code.
Usage
/ci # Run all gates
/ci --quick # Lint + build only
/ci --security # All gates + extra security
Pipeline Gates
Execute gates sequentially. Stop on first failure.
Gate 1: Lint & Format
# Detect project type and run appropriate linter
if [ -f "package.json" ]; then
npm run lint 2>/dev/null || npx eslint . --ext .js,.ts,.tsx
npm run format:check 2>/dev/null || npx prettier --check .
fi
if [ -f "pyproject.toml" ] || [ -f "setup.py" ]; then
ruff check . 2>/dev/null || python -m flake8 .
black --check . 2>/dev/null || true
fi
if [ -f "go.mod" ]; then
go fmt ./...
golangci-lint run 2>/dev/null || true
fi
Pass criteria: No lint errors, code formatted
Gate 2: Type Check
# TypeScript
if [ -f "tsconfig.json" ]; then
npx tsc --noEmit
fi
# Python
if [ -f "pyproject.toml" ]; then
mypy . 2>/dev/null || pyright . 2>/dev/null || true
fi
Pass criteria: No type errors
Gate 3: Build
# Node.js
if [ -f "package.json" ]; then
npm run build
fi
# Python
if [ -f "setup.py" ] || [ -f "pyproject.toml" ]; then
pip install -e . 2>/dev/null || python -m build
fi
# Go
if [ -f "go.mod" ]; then
go build ./...
fi
# Docker
if [ -f "Dockerfile" ]; then
docker build -t ci-test .
fi
Pass criteria: Build succeeds without errors
Gate 4: Test
# Node.js
if [ -f "package.json" ]; then
npm test -- --coverage --passWithNoTests
fi
# Python
if [ -f "pytest.ini" ] || [ -f "pyproject.toml" ]; then
pytest --cov --cov-fail-under=80 2>/dev/null || pytest
fi
# Go
if [ -f "go.mod" ]; then
go test -cover ./...
fi
Pass criteria: Tests pass, coverage >= 80% (if enforced)
Gate 5: Security Scan
# Node.js dependencies
if [ -f "package-lock.json" ]; then
npm audit --audit-level=high
fi
# Python dependencies
if [ -f "requirements.txt" ]; then
pip-audit 2>/dev/null || safety check 2>/dev/null || true
fi
# Secret detection
npx secretlint "**/*" 2>/dev/null || \
gitleaks detect --source . 2>/dev/null || \
trufflehog filesystem . 2>/dev/null || \
echo "No secret scanner available - manual review required"
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.
- 5d ago First seen · 233 lines · 16 tokens per session scan A 9117631ae029
ci is a command published in the GitHub repository ilyasibrahim/claude-agents-coordination (83 stars, last pushed 3mo ago), licensed Unlicense. It adds 16 tokens to every session and 1,424 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-30.
Other commands, from other repositories
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
actions
Command "actions" from openclaw/crabbox, covering actions, subcommands, hydrate, register and dispatch.
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.