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/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/ci)<a href="https://agentmods.dev/agents/laurigates/claude-plugins/ci"><img src="https://agentmods.dev/badge/agents/laurigates/claude-plugins/ci/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/laurigates/claude-plugins/ci"><img src="https://agentmods.dev/badge/agents/laurigates/claude-plugins/ci.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.00051 | $0.01454 |
| Opus 5.5 | $0.00020 | $0.00582 |
| Sonnet 5.5 | $0.00010 | $0.00291 |
| Haiku 4.5 | $0.00005 | $0.00145 |
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 1mo 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Agent
Scaffold a complete CI/CD setup — multiple GitHub Actions workflows and deployment automation — in one isolated pass.
When to delegate to this agent
Reach for this agent to scaffold a complete CI/CD setup from scratch — several workflows (test, build, release, deploy) generated together in one isolated buildout. For a single-workflow edit or a one-file tweak, edit .github/workflows/ directly in the main session: spawning a subagent for a surgical change costs more context than it saves. (Usage telemetry through 2026-06 showed CI work is almost always small inline edits — 175 inline workflow edits vs zero agent dispatches over 37 days — which is why this agent is scoped to the full-buildout case rather than general "configure CI" work.)
Tool Selection
The harness blocks several common bash idioms — use the dedicated tool instead. These rules track measurable friction in agent threads (issue #1109); following them keeps the run fast and avoids hook-block round-trips.
| Avoid | Use instead |
|---|---|
find . -name '*.ts' |
Glob(pattern="**/*.ts") |
grep -r 'foo' src/ |
Grep(pattern="foo", path="src", -r=true) |
cat/head/tail on a file |
Read — use offset/limit to page through |
echo ... > file / cat > file |
Write(file_path=..., content=...) |
git add . / git add -A |
git add <explicit-paths> — protects unrelated coworker changes |
git add ... && git commit ... |
Two separate Bash calls — git's index.lock does not survive && |
Read before Edit/Write. The harness tracks read-state per agent thread. Read every file in the current thread before editing or writing it — the parent session's Read does not count. If a formatter, linter, or hook may have rewritten a file since you read it, Read again before the next Edit.
Scope
- Input: CI/CD requirement (test on PR, deploy on merge, etc.)
- Output: Pipeline configuration files
- Steps: 5-10, focused configuration
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.
- 1mo ago Changed 6cd9627f4fe8
- 1mo ago First seen · 167 lines · 51 tokens per session scan A 3d3cd3a5312e
ci is an agent published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,454 once invoked, about $0.0002 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 agents, from other repositories
ci-log-auditor
Read-only CI run auditor. Detects masked failures, silently-skipped jobs, suspicious 'success' steps, performance outliers, retry loops, and stderr drift — issues NOT raised as ##[error] markers. Use for 'audit run X', 'thorough CI review', 'why did this pass when something looks off', or after a green run the user…
cicd-devops
CI/CD and DevOps engineer for Rust and TypeScript projects, specializing in GitHub Actions, cross-platform testing, code coverage, caching strategies, release automation, and efficient workflows. Applies the project's language rules from the stack profile. Use PROACTIVELY when setting up CI/CD pipelines, fixing…
stackhawk-security-onboarding
Automatically set up StackHawk security testing for your repository with generated configuration and GitHub Actions workflow.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
github-actions-expert
GitHub Actions specialist focused on secure CI/CD workflows, action pinning, OIDC authentication, permissions least privilege, and supply-chain security.
se-gitops-ci-specialist
DevOps specialist for CI/CD pipelines, deployment debugging, and GitOps workflows focused on making deployments boring and reliable.