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.
git clone --depth 1 https://github.com/sodam-ai/SoDam-AgentWrote 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/sodam-ai/sodam-agent/cicd-manager)<a href="https://agentmods.dev/agents/sodam-ai/sodam-agent/cicd-manager"><img src="https://agentmods.dev/badge/agents/sodam-ai/sodam-agent/cicd-manager/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/sodam-ai/sodam-agent/cicd-manager"><img src="https://agentmods.dev/badge/agents/sodam-ai/sodam-agent/cicd-manager.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.00019 | $0.00092 |
| Opus 5 | $0.00010 | $0.00046 |
| Sonnet 5 | $0.00004 | $0.00018 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade A, and why
cicd-manager 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 11d 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
당신은 CI/CD 관리자입니다. 빌드·테스트·배포 자동화 워크플로우(예: GitHub Actions)를 구성하고 점검합니다. 실패 시 원인을 바로 알 수 있는 로그·알림을 함께 설계하세요.
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.
- 11d ago First seen · 9 lines · 19 tokens per session scan A 0d61b7e28c72
cicd-manager is an agent published in the GitHub repository sodam-ai/SoDam-Agent (15 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 92 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 agents, from other repositories
DevOps Engineer
CI/CD pipelines, deployment strategies, infrastructure as code, and container orchestration.
devops-engineer
Use when you need to configure Docker containers, set up CI/CD pipelines, manage cloud infrastructure, configure monitoring, or handle deployment automation.
ci-cd-specialist
Use when you need to design, implement, or troubleshoot CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins, ArgoCD), deployment strategies, or release automation workflows.
ci-fixer
Diagnose and fix failing GitHub CI on your own PRs. Fetches Actions logs, queries repo CI history for prior patterns, summarizes failures, drafts a fix plan, and implements after explicit approval. Hard stop if PR belongs to someone else or has human reviewer comments. Use when PR checks fail and you need root-cause…
devops
Infrastructure, CI/CD, and deployment specialist. Use for Docker, CI pipelines, deployment scripts, monitoring, and infrastructure-as-code. Use proactively when touching Dockerfiles, workflows, or deployment config.
release-ci-engineer
Release engineering and CI/CD specialist for GitHub Actions pipelines, release-please automation, semantic versioning, changelogs, branch protection, flaky-test diagnosis, and runner cost optimization. Use for: CI failures and diagnostics, release-please gate issues, version bumps and changelogs…