A project-specific guide for designing, changing, and operating CarpeOS's GitHub Actions workflows and local check scripts. GitHub Actions is GitHub's system for running automated build and test jobs.

Use it when changing workflows, package scripts, tests, smoke or end-to-end checks, branch protection, release jobs, or Product 4 evaluation workflows.

It helps keep CI, or automated code checks, consistent and prevents new checks from making pull requests slow, noisy, or unreliable.

carpeos-ci — Skill for Claude Code and Codex by innocarpe/CarpeOS

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/innocarpe/CarpeOS

agentmods

npx agentmods add skills/innocarpe/carpeos/carpeos-ci

Made for: Claude Code, Codex.

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

README.md

[![agentmods](https://agentmods.dev/badge/skills/innocarpe/carpeos/carpeos-ci/github.svg)](https://agentmods.dev/skills/innocarpe/carpeos/carpeos-ci)

Your own site

<a href="https://agentmods.dev/skills/innocarpe/carpeos/carpeos-ci"><img src="https://agentmods.dev/badge/skills/innocarpe/carpeos/carpeos-ci/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/innocarpe/carpeos/carpeos-ci"><img src="https://agentmods.dev/badge/skills/innocarpe/carpeos/carpeos-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 106 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,483 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00106	$0.02483
Opus 5.5	$0.00042	$0.00993
Sonnet 5.5	$0.00021	$0.00497
Haiku 4.5	$0.00011	$0.00248

Measured 1mo ago against content hash 89be89eb6602, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

carpeos-ci 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 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.

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.

skills/carpeos-ci/SKILL.md · 231 lines

How it starts

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

CarpeOS CI (shared harness skill)

Same standard for Claude Code, Codex CLI, Grok Build, and Gajae Code/GJC.

Do not grow CI ad hoc. Load this skill and the policy SSOT before adding, moving, or “temporarily” wiring any check.

Source of truth

Artifact	Path
Policy SSOT	`docs/maintainers/ci-policy.md`
Primary workflow	`.github/workflows/ci.yml`
Secret scan	`.github/workflows/secret-scan.yml`
Trust plane (gated)	`.github/workflows/product-4-candidate-*.yml`
Release	`.github/workflows/release.yml`
Local entrypoints	root `package.json` (`check`, `test`, `smoke:*`)
Agent rules	`AGENTS.md` / `Agents.md` (CI section)

Read docs/maintainers/ci-policy.md in full before changing workflows or check composition. This skill is the operating procedure; the doc is the contract.

When to use

Trigger on any of:

edit under .github/workflows/;
change pnpm check / test / smoke / e2e scripts used by CI;
“CI is slow”, “Actions is red noise”, “add a required check”;
Product 4 evaluate / attest / publish workflow work;
proposal to run heavy evals on every PR;
after a merge that reintroduces invalid workflow YAML.

Hard rules (fail closed)

Lanes first. Every check belongs to exactly one default lane:
- pr-lean — merge-blocking, budgeted for iteration;
- main-full — deeper integration after merge;
- trust-release — Product 4 / release authority planes;
- local-only — agent/human, not GHA.
PR lean budget. Target ≤ 2 minutes wall clock on ubuntu-latest with warm cache. If a change would push PR Checks > 3 minutes, stop and either re-home work to main-full / tests or get explicit maintainer approval in the PR Why section.
No duplicate monorepo work on PR. Do not rebuild packages already built by pnpm check (or the lean equivalent) only to run a short eval on every PR.
Prefer tests over new workflows. New invariants land as package tests or scripts/test/*.test.mjs first. New YAML needs the change-gate table.
Job-level env must not reference runner.*. Use step with: / run: or a setup step + GITHUB_ENV. Invalid workflow files (0s, path-as-name) are P0.
Trust plane is not default PR CI. Product 4 candidate workflows are not required merge gates until activation policy says so. Logic is enforced by unit/contract tests; live GHA may be off, dispatch-only, or non-required.
Release credentials never on PR. No npm tokens, signing keys, or checks-write App privileges on untrusted pull_request jobs.
Same commands locally. Agents reproduce CI with root pnpm / node --test scripts. Do not invent CI-only unverifiable glue.
Harness-neutral. Do not add “Claude-only” or “Grok-only” CI rules. Update this skill + docs/maintainers/ci-policy.md instead.
Honest PR validation. When CI changes, the PR validation table lists real commands and results (carpeos-pr skill).

Read the full file on GitHub · 231 lines

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.

1mo ago First seen · 231 lines · 106 tokens per session scan A 89be89eb6602

Subscribe to this mod's changes

carpeos-ci is a skill published in the GitHub repository innocarpe/CarpeOS (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 106 tokens to every session and 2,483 once invoked, about $0.0004 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-31.

CI and CD DevOps and cloud ai-agents cloudflare knowledge-management local-first mcp obsidian

enzyme-sqlite-source

Connect an unfamiliar SQLite database to Enzyme without changing the source data. Inspect the database, decide which query columns represent identity, people, time, content, and folders, show real examples for approval, save a workspace program in the Enzyme language, and verify init and refresh. Use for email…

byenzyme/enzyme · 83 tokens

enzyme-workspace-setup

Set up or check Enzyme in a Markdown workspace. Use for first setup, re-setup, diagnosis, or requested cleanup; existing Enzyme files do not prove setup is complete. Write settings from the user's own map of their notes, review them with the user, demonstrate an answer from real notes, and repair only an evidenced…

byenzyme/enzyme · 91 tokens

enzyme

Use Enzyme in an already activated Obsidian, Markdown, or Hermes workspace for working-memory retrieval, source-grounded exploration, search by keyword and meaning, runtime note-writing, and refresh. If the workspace is not initialized, follow the first-time setup section before normal retrieval.

byenzyme/enzyme · 58 tokens

llm-wiki

Maintain a personal team knowledge base using the LLM Wiki pattern — incremental ingest, query, and lint operations on a layered wiki architecture.

TheSmuks/ai-project-template · 31 tokens

wiki-build

A tool for building or rebuilding a local wiki from all source files in a vault, which is a folder used to store source material. It creates structured pages, layered indexes, logs, and cross-links.

zhuzhaoyun/Molio · 0 tokens

remotion

Molio's builtin skill for MAKING a video from any source — wiki notes, articles, scripts, product info, or a brief — and rendering it to MP4. Use whenever the user wants to create/produce a video: a product demo, promo, trailer, intro, explainer, motion graphic, kinetic typography, social clip, or animated logo — even…