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.
npx skills add alexei-led/cc-thingz --skill operating-infragit clone --depth 1 https://github.com/alexei-led/cc-thingzWrote 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/skills/alexei-led/cc-thingz/operating-infra)<a href="https://agentmods.dev/skills/alexei-led/cc-thingz/operating-infra"><img src="https://agentmods.dev/badge/skills/alexei-led/cc-thingz/operating-infra/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/skills/alexei-led/cc-thingz/operating-infra"><img src="https://agentmods.dev/badge/skills/alexei-led/cc-thingz/operating-infra.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00155 | $0.01169 |
| Opus 5.5 | $0.00062 | $0.00468 |
| Sonnet 5.5 | $0.00031 | $0.00234 |
| Haiku 4.5 | $0.00015 | $0.00117 |
Grade A, and why
operating-infra 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 24d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operate Infrastructure
Work from files, plans, logs, and read-only commands; edit repo files freely, but touch live resources only under these rules:
- Before any cloud command, confirm identity (
aws sts get-caller-identity --profile <profile>;gcloud auth list,gcloud config list), passing profile, project, region, and zone explicitly instead of relying on CLI defaults. - Before any live change that's destructive, costly, or externally visible (apply, upgrade, rollout, delete, destroy, stop, resize, scale, IAM, bucket, network, DDL/DML, rollback): show identity, exact resources (ARNs or names), blast radius, irreversibility, and the plan/diff/inventory behind them, then wait for explicit confirmation.
- Every apply, upgrade, or rollout, regardless of blast radius: confirm the exact destination first (account, context, namespace, workspace, or release — name production explicitly), run the validation gates below on the same rendered artifact, show the plan or diff with create/modify/delete counts, and apply only that same reviewed artifact (the saved plan file or rendered manifest), only after explicit confirmation of that exact artifact and destination — never apply to production without it.
- After applying, verify rollout status, pod health, or Terraform outputs/state, and name the rollback path. On apply failure or a timed-out/degraded rollout: stop, report status and rollback options, and ask before any rollback.
- Without write access, return proposed changes (file, change, reason) instead of applying them.
For troubleshooting: rank likely causes, gather one safe signal at a time, propose the next step. For authoring: pick the smallest pattern keeping ownership, state boundaries, and least privilege.
In GitHub Actions this skill owns workflow structure, triggers, permissions, runners, actions, environments, secrets, caching, and concurrency — not the shell body of a run: step (writing-shell); mixed changes use both.
References
Load every reference that matches the stack:
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .agentbundler/targets/claude.json 945 B
- references/aws.md 1.2 KB
- references/bigquery.md 1.4 KB
- references/cloud-run.md 1.1 KB
- references/deploying.md 4.5 KB
- references/dockerfile.md 987 B
- references/gcp.md 1.1 KB
- references/github-actions.md 1.3 KB
- references/helm.md 982 B
- references/kubernetes.md 1.7 KB
- references/linux.md 1001 B
- references/terraform.md 1.7 KB
- scripts/bq-cost-check.py 5.0 KB runs code
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.
- 24d ago Changed · +1 lines 40096a55e9a9
- 25d ago Changed · +5 lines · +36 tokens per session 956ed5b29c6c
- 26d ago Changed · -21 lines 409c445f0064
- 1mo ago First seen · 85 lines · 119 tokens per session scan A 2df87eee1256
operating-infra is a skill published in the GitHub repository alexei-led/cc-thingz (38 stars, last pushed today), licensed MIT. It adds 155 tokens to every session and 1,169 once invoked, about $0.0006 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 skills, from other repositories
ring:hardening-dockerfiles
Hardening Dockerfiles to reach Docker Hub Health Score grade A: enforcing a non-root USER, minimal/distroless multi-stage base images, no fixable critical/high CVEs, no AGPL-3.0 deps, and SBOM+provenance attestations. Use when creating a new Dockerfile, auditing one for security, or preparing images for Docker Hub…
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.
aster-review-ci
Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers aster review --pr, --json, --stream, --comment, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically.
gemini-review
Google Gemini CLI code review with Gemini 2.5 Pro, 1M token context, CI/CD integration.
deployment
Use when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is coolify, vercel, railway, render), NOT the Dockerfile alone…
windows-image-updater
Automates Windows container image migration for OneBranch pipelines. Bumps AdoPipelineGeneration package, regenerates pipeline configs via ConfigGen, and verifies old image reference is removed. Use for LTSC2019 to LTSC2022 migration, container image updates, OneBranch pipeline image upgrades.