examples: Skill for Claude Code

.claude/skills/orchestrate:ci/SKILL.md

orchestrate:ci is a skill for Claude Code from rossoctl/examples. It costs 33 tokens per session (3,076 once invoked), scanned A, original, Apache-2.0.

A workflow for adding automated checks to a code repository. Continuous integration, or CI, runs checks automatically when code changes are proposed.

In plain words
What is it for?
Use it to inspect a repository's technology and missing checks, then create CI workflows and related configuration for testing, building, security scanning, dependency management, and action pinning.
Why use it?
It brings linting, tests, builds, security checks, dependency updates, and safeguards against unsafe build changes into one reviewable setup.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is rossoctl/examples's own configuration. It tells Claude Code how to work on examples itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything examples configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rossoctl/examples. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rossoctl/examples/main/.claude/skills/orchestrate:ci/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/rossoctl/examples

Made for: Claude Code.

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.

agentmods badge for orchestrate:ci

README.md
[![agentmods](https://agentmods.dev/badge/skills/rossoctl/examples/orchestrate-ci/github.svg)](https://agentmods.dev/skills/rossoctl/examples/orchestrate-ci)
Your own site
<a href="https://agentmods.dev/skills/rossoctl/examples/orchestrate-ci"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/orchestrate-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.

agentmods 80×15 button for orchestrate:ci

Your own site · 80×15
<a href="https://agentmods.dev/skills/rossoctl/examples/orchestrate-ci"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/orchestrate-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,076 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00033 $0.03076
Opus 5.5 $0.00013 $0.01230
Sonnet 5.5 $0.00007 $0.00615
Haiku 4.5 $0.00003 $0.00308

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

Security

Grade A, and why

orchestrate: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.

.claude/skills/orchestrate:ci/SKILL.md · 402 lines

How it starts

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

flowchart TD
    START(["/orchestrate:ci"]) --> READ["Read plan + scan report"]:::orch
    READ --> DETECT["Detect tech stack + CI gaps"]:::orch
    DETECT --> T1["Tier 1: Universal checks"]:::orch
    T1 --> T2{"Tier 2 needed?"}
    T2 -->|Yes| T2_GEN["Tier 2: Conditional checks"]:::orch
    T2 -->|No| T3
    T2_GEN --> T3{"Tier 3 needed?"}
    T3 -->|Yes| T3_GEN["Tier 3: Advanced patterns"]:::orch
    T3 -->|No| BRANCH
    T3_GEN --> BRANCH["Create branch"]:::orch
    BRANCH --> SIZE{Under 700 lines?}
    SIZE -->|Yes| PR["Commit + open PR"]:::orch
    SIZE -->|No| SPLIT["Split into sub-PRs"]:::orch
    SPLIT --> PR
    PR --> DONE([Phase complete])

    classDef orch fill:#FF9800,stroke:#333,color:white

Follow this diagram as the workflow.

Orchestrate: CI

Add comprehensive CI workflows to a target repository. This is Phase 4 and produces PR #3. Covers lint, test, build, security scanning, dependency management, and supply chain hardening.

When to Use

  • After orchestrate:plan identifies CI as a needed phase
  • After precommit and tests phases (so CI can run the test suite)

Prerequisites

  • Plan exists at /tmp/rossoctl/orchestrate/<target>/plan.md
  • Scan report at /tmp/rossoctl/orchestrate/<target>/scan-report.md
  • Target repo in .repos/<target>/

Read Scan Report First

Before generating anything, read the scan report to determine:

  • Tech stack (Python, Go, Node, Ansible, Rust, multi-language)
  • Existing CI workflows (what to preserve vs replace)
  • Dockerfiles present (triggers container build workflows)
  • Existing dependabot config (what ecosystems are covered)
  • Existing security scanning (what's already in place)

Tier 1: Universal Checks (Always Generate)

Every repo gets these regardless of tech stack.

1.1 Core CI Workflow (ci.yml)

Trigger: pull_request on main and push to main

Adapt to tech stack from scan report:

Language Lint Test Build
Python ruff check . + ruff format --check . pytest -v uv build (if pyproject.toml has build-system)
Go golangci-lint run go test ./... -v -race go build ./...
Node npm run lint npm test npm run build
Rust cargo clippy -- -D warnings cargo test cargo build --release
Ansible ansible-lint molecule test (if molecule config exists) —

Read the full file on GitHub · 402 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.

  1. 1mo ago First seen · 402 lines · 33 tokens per session scan A 0ad2344e6ee6

Subscribe to this mod's changes

orchestrate:ci is a skill published in the GitHub repository rossoctl/examples (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 3,076 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

atmos-profiles

Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.

cloudposse/atmos · 35 tokens

webhook-management

Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.

hoangsonww/Claude-Code-Agent-Monitor · 56 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens

managing-github-actions-secrets

Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.

PostHog/posthog-foss · 67 tokens

deployment-engineer

Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…

rmyndharis/antigravity-skills · 77 tokens