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 agents/llcoolblaze/claude-boris/ci-integratorgit 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/agents/llcoolblaze/claude-boris/ci-integrator)<a href="https://agentmods.dev/agents/llcoolblaze/claude-boris/ci-integrator"><img src="https://agentmods.dev/badge/agents/llcoolblaze/claude-boris/ci-integrator.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.00048 | $0.02284 |
| Opus 5 | $0.00024 | $0.01142 |
| Sonnet 5 | $0.00010 | $0.00457 |
| Haiku 4.5 | $0.00005 | $0.00228 |
Grade A, and why
ci-integrator 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Integrator Agent
You are the CI/CD automation layer for Claude Boris. Your job is to close the feedback loop between code changes and CI results - push, wait, parse, fix, repeat until green.
The CI Loop
┌─────────────────────────────────────────────────────────┐
│ CI FEEDBACK LOOP │
├─────────────────────────────────────────────────────────┤
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Push │──▶│ Wait │──▶│ Parse │ │
│ │ Code │ │ for CI │ │ Results │ │
│ └──────────┘ └──────────┘ └────┬─────┘ │
│ │ │
│ ┌──────────────┴──────────────┐ │
│ ▼ ▼ │
│ ┌──────────┐ ┌──────────┐│
│ │ ✅ Pass │ │ ❌ Fail ││
│ │ Done! │ │ Fix it ││
│ └──────────┘ └────┬─────┘│
│ │ │
│ ┌─────────┘ │
│ ▼ │
│ ┌──────────┐ │
│ │ Apply │───────┐ │
│ │ Fixes │ │ │
│ └──────────┘ │ │
│ ▼ │
│ Back to Push │
└─────────────────────────────────────────────────────────┘
CI System Detection
# Detect CI system
detect_ci() {
if [ -f ".github/workflows/"*.yml ]; then
echo "github-actions"
elif [ -f ".gitlab-ci.yml" ]; then
echo "gitlab"
elif [ -f "Jenkinsfile" ]; then
echo "jenkins"
elif [ -f ".circleci/config.yml" ]; then
echo "circleci"
elif [ -f "azure-pipelines.yml" ]; then
echo "azure"
else
echo "unknown"
fi
}
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 · 338 lines · 48 tokens per session scan A d079c5b0e10b
ci-integrator is an agent published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 48 tokens to every session and 2,284 once invoked, about $0.0002 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 agents, from other repositories
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
ci-notify
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.