ubuntu-bootstrap

A setup workflow for preparing Ubuntu or Debian machines to run a Cozystack Kubernetes cluster. It uses the upstream Cozystack Ansible playbooks, which automate configuration tasks across cluster nodes.

In plain words
What is it for?
Use it to create the Ansible inventory, prepare Ubuntu or Debian nodes, and configure them for Cozystack installation.
Why use it?
Preparing nodes by hand requires many system changes and can miss important settings or packages. The workflow collects the needed node details and runs the existing preparation steps consistently.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/cozystack/ccp/ubuntu-bootstrap
Any agent
npx skills add cozystack/ccp --skill ubuntu-bootstrap
Clone the repo
git clone --depth 1 https://github.com/cozystack/ccp

Made for: Claude Code, Codex.

Per session 233 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,356 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00233 $0.05356
Opus 5 $0.00117 $0.02678
Sonnet 5 $0.00047 $0.01071
Haiku 4.5 $0.00023 $0.00536

Measured 2d ago against content hash b6045c45e302, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

ubuntu-bootstrap scanned grade D with 2 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 2d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

This is the **one** interview phase. After Phase 1 inventory interview the skill auto-fills everything the rest of the flow needs and presents a single consolidated summary; later phases (ansible-playbook prepare-sudo /

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

Offer optional merge into `~/.kube/config` via `kubectl kc add --file "$CONFIG_DIR/kubeconfig.yaml" --context-name "$CLUSTER_CONTEXT" --cover`. Default: keep standalone — `$CONFIG_DIR/kubeconfig.yaml` is gitignored, the
plugins/cozystack/skills/ubuntu-bootstrap/SKILL.md · 377 lines

How it starts

The opening of the file, as written. The whole thing — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.

cozystack:ubuntu-bootstrap

Work in reasoning mode. Use the phrasing cozystack:ubuntu-bootstrap. Announce phase transitions: cozystack:ubuntu-bootstrap Phase N — <name>.

Note on language in this SKILL.md — every operator-facing prompt below is written in English for clarity. At runtime the skill matches the operator's natural language detected from prior conversation messages (or read from <config-dir>/.state.yaml operator_language when the wizard chain is in progress). Code identifiers, commands, file paths, and any text destined for GitHub stay canonical. Ansible task names from upstream playbooks come through in English by design — don't translate them.

Why this is an ansible wrapper, not a hand-rolled SSH flow

cozystack/ansible-cozystack/examples/ubuntu/ already implements every node-prep step Cozystack needs — and that list is non-obvious and broad: 11 sysctl keys, 8 kernel modules across required / optional / DRBD / ZFS / KubeVirt categories, LINBIT PPA wiring for drbd-dkms on Secure Boot, multipath blacklist for drbd* devnodes, iptables flush for cloud images that REJECT non-SSH traffic, Ubuntu 26.04 sudo-rs workaround. A hand-rolled SSH shell skill drifts from this list the moment ansible-cozystack adds anything new. Wrapping the playbooks keeps ubuntu-bootstrap aligned by reference.

The wrapper does not call the cozystack-install step from upstream site.yml — that lives in cozystack:cluster-install so the storage / extractedprism / OIDC / domain logic stays in one place. The skill renders an inventory with cozystack_create_platform_package: false to enforce this.

Cluster config directory

Every artifact lives under <config-dir>/. Default resolution (read from state.config_dir written by cozystack:wizard):

<config-dir>/
  .gitignore                          # skill-managed: excludes secrets + state
  .state.yaml                         # wizard chain state (read+write by every skill)
  inventory.yml                       # ansible inventory rendered by this skill
  kubeconfig.yaml                     # k3s kubeconfig after Phase 8 (server URL rewritten)

Read the full file on GitHub · 377 lines

Files

What ships with it

3 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.

Changes

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.

  1. 2d ago First seen · 377 lines · 233 tokens per session scan D b6045c45e302

Subscribe to this mod's changes

ubuntu-bootstrap is a skill published in the GitHub repository cozystack/ccp (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 233 tokens to every session and 5,356 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens