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/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/byerlikaya/claude-starter-kit/devops-expert-csk"><img src="https://agentmods.dev/badge/agents/byerlikaya/claude-starter-kit/devops-expert-csk.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.00114 | $0.01739 |
| Opus 5.5 | $0.00046 | $0.00696 |
| Sonnet 5.5 | $0.00023 | $0.00348 |
| Haiku 4.5 | $0.00011 | $0.00174 |
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 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.
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 — 81 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, in this order: CI/CD pipeline (first) · production incident · deploy to a server
(fallback). 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)
Ask first: does this project already have a CI/CD pipeline? That answer decides the shape of the whole job,
and it is a question to settle by looking (ls .github/workflows .gitlab-ci.yml Jenkinsfile azure-pipelines.yml),
never by assuming.
- No pipeline → author one (
ci-pipeline): a workflow file for the host this project actually uses, built from that skill's stages (lint→build→test→quality→security→artifact). - A pipeline exists → it is yours to read and keep correct (
ci-pipeline): read it before changing anything, carry the change into it, trigger and watch runs (gh run …/glab ci …), and diagnose a failing job from its LOG, never from the status icon. The deploy itself belongs to the runner, not to you — your part is the promotion decision, its approval, and a health check from OUTSIDE the platform afterwards (deploy, B). - No pipeline AND a server to ship to → the fallback (
deploy, A · self-managed host): you perform the swap over SSH yourself, with the backup, health gate and rollback that skill requires. Last resort, not the default — a project that has a pipeline never gets a hand-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.
- 1mo ago Changed be96de2b012c
- 1mo ago Changed · +17 lines · +53 tokens per session bd91fc9ec034
- 1mo 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 (24 stars, last pushed 28d ago), licensed MIT. It adds 114 tokens to every session and 1,739 once invoked, about $0.0005 per session on Opus 5.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
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
stock-balance-sheet-reviewer
Specialist for US-stock balance-sheet health review — leverage (Net Debt/EBITDA), liquidity (current ratio, cash runway), goodwill concentration and impairment history, working capital trends (DSO, inventory days), off-balance-sheet items (commitments, contingencies), and pension underfunding. Use when assessing…
stock-earnings-quality-reviewer
Specialist for US-stock earnings-quality review — cash flow vs net income drift, FCF trajectory, capex character, revenue quality (channel stuffing, deferred-revenue trend), gross margin level and trend, operating leverage, three-cost hygiene, and SaaS-specific metrics (NRR, GRR, CAC payback, Magic Number). Use when…