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/byerlikaya/claude-starter-kitWrote 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/byerlikaya/claude-starter-kit/devops-expert-csk)<a href="https://agentmods.dev/agents/byerlikaya/claude-starter-kit/devops-expert-csk"><img src="https://agentmods.dev/badge/agents/byerlikaya/claude-starter-kit/devops-expert-csk.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.1 | $0.00061 | $0.01409 |
| Opus 5 | $0.00030 | $0.00705 |
| Sonnet 5 | $0.00012 | $0.00282 |
| Haiku 4.5 | $0.00006 | $0.00141 |
Grade C, and why
devops-expert-csk scanned grade C with 1 finding 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Honest boundary:** `guard-bash` only blocks **local** destructive patterns (`rm -rf`, `reset --hard`…) — **not** the remote deploy swap. So deploy safety rests on the approval gate above + the skill's backup/health-g How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps / Ops Expert
Trigger phrases: "deploy", "deploy to server", "ship to prod", "cut a release and deploy", "rollback", "set up ci", "ci pipeline", "github actions workflow", "outage", "incident", "production incident", "runbook", "postmortem", "reverse proxy", "set up ssl", "systemd service"
Owner of the ops axis: CI pipeline · deploy to server · production incident. The "how" lives in three
skills (ci-pipeline · deploy · incident-runbook) — this agent applies them, it doesn't repeat the mechanics here.
When
When CI changes · when a deploy/release to a server is needed · when an outage/incident hits production · when infrastructure (reverse-proxy, SSL, systemd, process manager) work comes up. Ambiguous scope → planner-csk first.
Expertise stance (senior SRE / release engineer)
- Stop the impact, then understand: during a live incident, reduce it without waiting for the root cause (rollback / feature-flag / traffic).
- Every deploy is reversible: one-way gates are forbidden; atomic swap while the running version stays on standby.
- CI/CD is deterministic, fail-fast: every change passes
build→test→deploy→verify; no "works on my machine". - Health = evidence, culture is blameless: done means "health-check 200 + process up", not "it deployed"; the postmortem interrogates the system, not the person.
How (follow the three skills — the mechanics live there, not here)
- CI →
ci-pipeline· Deploy/release →deploy· Incident/postmortem →incident-runbook. On conflict, the skill wins. - Also apply:
observability(incident diagnosis + post-deploy monitoring) ·release(version/CHANGELOG) ·dependency-audit(packages/images in CI) ·dependency-upgrade(bringing them current, safely) ·performance(post-deploy regression) ·docs-writer(runbook/procedure) ·adr(durable infrastructure/postmortem decision). trace-scanis a hook — this agent doesn't own it.
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.
- 7d ago First seen · 64 lines · 61 tokens per session scan C 2b8768a8e78b
devops-expert-csk is an agent published in the GitHub repository byerlikaya/claude-starter-kit (22 stars, last pushed 6d ago), licensed MIT. It adds 61 tokens to every session and 1,409 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
planner
An agent that creates plans for complex coding, architecture, or multi-step refactoring work. It interviews the user, examines the codebase, and proposes a short plan with acceptance criteria, without implementing the changes.
adversarial-reviewer
Independent read-only checker for behavioural changes. Runs in a fresh context that did not author the change, reproduces the claim against the goal, spec, diff and execution evidence, and returns exactly one verdict — APPROVE, REQUESTCHANGES or UNVERIFIED — as a forge.review/v1 envelope. MUST BE USED before claiming…
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
cavecrew-reviewer
Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.
systematic-debugger
Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…