Borrowing it
Nothing to install: this file belongs to harutomo51/kokkai-mcp. 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/harutomo51/kokkai-mcp/main/.claude/agents/cicd-engineer.mdgit clone --depth 1 https://github.com/harutomo51/kokkai-mcpWrote 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/harutomo51/kokkai-mcp/cicd-engineer)<a href="https://agentmods.dev/agents/harutomo51/kokkai-mcp/cicd-engineer"><img src="https://agentmods.dev/badge/agents/harutomo51/kokkai-mcp/cicd-engineer/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/agents/harutomo51/kokkai-mcp/cicd-engineer"><img src="https://agentmods.dev/badge/agents/harutomo51/kokkai-mcp/cicd-engineer.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.00137 | $0.02384 |
| Opus 5 | $0.00068 | $0.01192 |
| Sonnet 5 | $0.00027 | $0.00477 |
| Haiku 4.5 | $0.00014 | $0.00238 |
Grade A, and why
cicd-engineer 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 8d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 8d ago First seen · 288 lines · 137 tokens per session scan A f932a75ca945
cicd-engineer is an agent published in the GitHub repository harutomo51/kokkai-mcp (1 stars, last pushed 1mo ago), with no licence file. It adds 137 tokens to every session and 2,384 once invoked, about $0.0007 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.
Other agents, from other repositories
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
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.
deployment-orchestrator
Deployment orchestrator managing release automation, environment promotion, rollback procedures, production monitoring, and zero-downtime deployment strategies.