Agent skill

Cosa Basics

by coreos in coreos/coreos-assembler

Initialize a COSA workdir, build or fetch Fedora CoreOS images, and launch local QEMU VMs using coreos-assembler

Apache-2.0Auto-check passed

Install Cosa Basics

skills CLI
$ npx skills add coreos/coreos-assembler --skill cosa-basics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install coreos/coreos-assembler cosa-basics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/coreos/coreos-assembler.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cosa-basics .claude/skills/cosa-basics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cosa-basics
GitHub stars
395
Token cost
~1.8k tokens
SKILL.md length
945 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
Apache-2.0

At a glance

Initialize a COSA workdir, build or fetch Fedora CoreOS images, and launch local QEMU VMs using coreos-assembler

  • Works in 3 steps: Set up a COSA workdir → Obtain a build → Launch the VM
  • SKILL.md covers Out of scope, Key documentation references, Running COSA and Workflow, plus 1 more section
  • Calls podman; reaches github.com

What it does

Cosa Basics is an agent skill from coreos/coreos-assembler. Initialize a COSA workdir, build or fetch Fedora CoreOS images, and launch local QEMU VMs using coreos-assembler

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Bash. The repository describes itself as: Tooling container to assemble CoreOS-like systems. The licence is Apache-2.0.

Example prompts

  • “/cosa-basics”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Set up a COSA workdir
  2. Obtain a build
  3. Launch the VM

What it can do on your machine

Read from SKILL.md and the folder at commit 4ab8b08. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • podman

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cosa Basics loads about 1.8k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 945 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from coreos/coreos-assembler at commit 4ab8b08, republished under its Apache-2.0 licence (© coreos). 945 words, ~1,757 tokens.

Download SKILL.mdSave it as .claude/skills/cosa-basics/SKILL.md (or your agent's skills folder).
name
cosa-basics
description
Initialize a COSA workdir, build or fetch Fedora CoreOS images, and launch local QEMU VMs using coreos-assembler

COSA Basics

This skill guides you through the core coreos-assembler (COSA) workflow: initializing a build directory, obtaining a CoreOS build (either from source or by fetching a published build), and launching a local QEMU VM.

Out of scope

Cloud platform image building and uploading (AWS, GCP, Azure, etc.) are not covered here. Load the cosa-platforms skill for those workflows.

Key documentation references

Do NOT duplicate these docs. Read them at runtime for command details:

FileWhat it covers
docs/building-fcos.mdFull build walkthrough, prerequisites, the cosa() bash alias
docs/cosa.mdCommand reference overview (all cosa subcommands)
docs/cosa/run.mdDetailed cosa run and QEMU VM options
docs/working.mdOverrides, customization, advanced usage
docs/devel.mdRunning cosa locally outside a container
src/cmd-initcosa init source -- all supported flags
src/cmd-buildfetchcosa buildfetch source -- all supported flags

Running COSA

Container mode (default)

COSA is designed to run inside a container. The container image is:

quay.io/coreos-assembler/coreos-assembler

Before running any cosa commands, read docs/building-fcos.md and extract the cosa() bash alias function defined there. This alias wraps podman run with the necessary privileges, device mounts (/dev/kvm, /dev/fuse), user namespace mapping, and volume mounts. The current working directory is mounted as /srv/ inside the container.

Set up the alias in the user's shell before running any cosa commands.

Local mode (for cosa developers)

Developers who have cosa installed locally can run commands directly without the container wrapper. Read docs/devel.md for details on this workflow. The commands themselves are the same; only the execution environment differs.

Workflow

Step 1: Set up a COSA workdir
  1. Ask the user for a working directory path. Default to ./fcos if they don't specify one.
  2. If the directory does not exist, create it.
  3. cd into the directory.
  4. Set up the cosa() bash alias (read it from docs/building-fcos.md).
  5. Initialize the workdir:
cosa init https://github.com/coreos/fedora-coreos-config

The user can override the config repo URL. Additional useful flags (read src/cmd-init for the full list):

  • --branch BRANCH -- use a specific branch of the config repo
  • --variant VARIANT -- select a build variant
  • --force -- allow init in a non-empty directory

After init, the directory structure will contain src/config/ (the cloned config repo), plus builds/, cache/, tmp/, and overrides/ directories that are populated during builds.

Step 2: Obtain a build

Choose one of the following paths based on what the user wants to do.

Option A: Build from source

This builds a fresh CoreOS image from the config repo and RPM sources:

cosa build
cosa osbuild qemu

cosa build creates the bootable OCI container (ostree commit). cosa osbuild qemu derives a QEMU disk image from that container. Both are required before cosa run will work.

Note: cosa fetch is a no-op in the current build flow. Package fetching happens automatically inside cosa build via buildah.

Show full SKILL.md (501 more words)Show less
Option B: Fetch an existing published build

This downloads a previously published build from the Fedora CoreOS build servers. Use this when you want to test or inspect an existing release without building from source.

Default flags: Include --artifact qemu --decompress when the user needs a local QEMU disk image (e.g. for cosa run or QEMU-based kola tests). The published artifacts are stored compressed on the server; --decompress expands them so the resulting qcow2 can be used directly.

If the user only needs to run tests on a cloud platform where images already exist (e.g. AMIs in AWS), --artifact and --decompress are not needed. A plain cosa buildfetch -b <build-id> fetches only a few small metadata files (including meta.json), which contain cloud image references that kola picks up automatically. See the cosa-platforms skill for details.

Fetch the latest build for a stream:

cosa buildfetch --stream <stream> --artifact qemu --decompress

Available streams: stable, testing, testing-devel, next, rawhide

If the user does not specify a stream, default to stable.

Fetch a specific build by ID:

cosa buildfetch -b <build-id> --artifact qemu --decompress

When -b/--build is given, --stream is not required -- the stream is auto-detected from the build ID's version number (the third dotted component maps to a stream, e.g. .2. = testing, .3. = stable). Read src/cmd-buildfetch for the full version-to-stream mapping. If --stream is also provided it must match or the command will error.

If the user wants a non-qemu artifact: replace --artifact qemu with the appropriate artifact name (e.g., metal, aws, gcp). But note that cloud platform workflows are better served by the cosa-platforms skill.

Step 3: Launch the VM
cosa run

This launches a QEMU VM using the latest build image with -snapshot (changes are discarded on exit). By default it establishes an SSH connection with auto-login as the core user.

Common options (read docs/cosa/run.md for the full list):

FlagPurpose
-c / --devshell-consoleUse serial console instead of SSH (see full boot, GRUB menu)
--qemu-image PATHUse a specific qcow2 image instead of the latest build
-B / --butane PATHPass a Butane config for the VM
-i / --ignition PATHPass an Ignition config for the VM
--add-disk SIZE[:OPTS]Attach additional disks
--kargs 'ARGS'Append kernel arguments
-m SIZESet VM memory in MB

Exiting the VM:

  • SSH mode: exit or Ctrl-D
  • Console mode: Ctrl-a x

Important notes

  • Each cosa command (via the alias) creates a transient container. Use cosa shell for a persistent interactive session inside the container.
  • /dev/kvm is required for both building disk images and running VMs. The host must be bare metal or have nested virtualization enabled.
  • The build directory at $PWD is mounted at /srv/ inside the container. Build artifacts persist across container invocations.
  • The workdir's builds/latest symlink always points to the most recent build.
  • To run kola tests against a build, load the cosa-kola skill. It covers test discovery, cosa kola run, upgrade tests, and result inspection.
  • Fedora infrastructure services (like Bodhi or Koji) are behind Anubis to prevent abuse. When querying APIs or web pages for information set a User-Agent and Accept headers to increase the chance of making it through unchallenged.

© coreos, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/cosa-basics of coreos/coreos-assembler.

Open the folder on GitHubat commit 4ab8b08

Compare with similar skills

Cosa Basics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cosa Basics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cosa Basics this skillcoreos/coreos-assembler395—~1.8kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k11 repos~4.1kAutomated safety check: NotesApache-2.0
Plugin Settings Patternanthropics/claude-plugins-official38k7 repos~3kAutomated safety check: PassApache-2.0
Mole Bug Patternstw93/Mole70k—~2kAutomated safety check: PassGPL-3.0
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
E2Ecallstack/react-native-pager-view3.4k1 repos~2.1kAutomated safety check: PassMIT

Similar skills

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Plugin Settings Pattern

    anthropics/claude-plugins-official

    Official

    Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.

    38k GitHub starsUsed in 7 repos~3k tokens
    Agent WorkflowsAuto-check passed
  • A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

    70k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 7 days ago
    Agent WorkflowsAuto-check passed
  • E2E

    callstack/react-native-pager-view

    Agentic end-to-end tests with e2e, the e2e runner. An agent skill from callstack/react-native-pager-view.

    3.4k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

More from coreos/coreos-assembler

  • Cosa Dev

    coreos/coreos-assembler

    Develop and test changes to coreos-assembler itself -- build mantle Go binaries (kola, ore, plume), iterate on Python/shell scripts, or do full container rebuilds

    395 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Cosa Kola

    coreos/coreos-assembler

    Run kola tests against CoreOS builds using coreos-assembler, including native and external tests

    395 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cosa Platforms

    coreos/coreos-assembler

    Build disk images, upload to cloud providers, and run tests or spawn instances on non-QEMU platforms (AWS, GCP, Azure, ISO, metal, etc.)

    395 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check: warnings

Works with

Questions about Cosa Basics

What does Cosa Basics do?

Initialize a COSA workdir, build or fetch Fedora CoreOS images, and launch local QEMU VMs using coreos-assembler. Cosa Basics is an agent skill from coreos/coreos-assembler.

How do I install Cosa Basics in Claude Code?

Run `npx skills add coreos/coreos-assembler --skill cosa-basics -a claude-code`. Or copy the skill folder (.agents/skills/cosa-basics in coreos/coreos-assembler) into .claude/skills/cosa-basics in your project. Claude Code loads it when a task matches its description.

How do I install Cosa Basics in Codex?

Run `npx skills add coreos/coreos-assembler --skill cosa-basics -a codex`. Or copy the skill folder (.agents/skills/cosa-basics in coreos/coreos-assembler) into .agents/skills/cosa-basics in your project. Codex loads it when a task matches its description.

Can I use Cosa Basics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coreos/coreos-assembler --skill cosa-basics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cosa-basics, .gemini/skills/cosa-basics, .github/skills/cosa-basics and .opencode/skills/cosa-basics in your project.

What does Cosa Basics need to run?

Going by SKILL.md and its folder, Cosa Basics needs the command-line tools its instructions call (podman).

Does Cosa Basics access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Cosa Basics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cosa Basics use?

Cosa Basics is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cosa Basics use?

About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cosa Basics?

Skills that share tags, products or a category with Cosa Basics: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Plugin Settings Pattern (anthropics/claude-plugins-official, 38k stars), Mole Bug Patterns (tw93/Mole, 70k stars) and Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cosa Basics?

coreos (a GitHub organization) maintains it in coreos/coreos-assembler, which has 395 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.

Source: coreos/coreos-assembler on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.