A local check for a Harmont CI pipeline, which is the automated process that builds and tests a project. It runs the pipeline with hm run inside Docker containers, then helps diagnose failures before code is pushed.

Use it after finishing a feature or fix, when preparing a pull request, or when you need to make Harmont CI pass locally.

It catches broken build or test steps on your machine before they reach remote CI or a pull request.

How harmont-dev/harmont-cli configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to harmont-dev/harmont-cli. 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/harmont-dev/harmont-cli/main/.claude/skills/validate-ci/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/harmont-dev/harmont-cli

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/harmont-dev/harmont-cli/validate-ci/github.svg)](https://agentmods.dev/skills/harmont-dev/harmont-cli/validate-ci)

Your own site

<a href="https://agentmods.dev/skills/harmont-dev/harmont-cli/validate-ci"><img src="https://agentmods.dev/badge/skills/harmont-dev/harmont-cli/validate-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/harmont-dev/harmont-cli/validate-ci"><img src="https://agentmods.dev/badge/skills/harmont-dev/harmont-cli/validate-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 545 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.00060	$0.00545
Opus 5.5	$0.00024	$0.00218
Sonnet 5.5	$0.00012	$0.00109
Haiku 4.5	$0.00006	$0.00055

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

Security

Grade A, and why

validate-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 2mo 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/validate-ci/SKILL.md · 39 lines

How it starts

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

Validate that the project's CI pipeline passes. Run the pipeline locally with hm run, diagnose and fix any failures, and only push to remote once local CI is green.

When to use

The user asks you to "make CI green", "run CI", "validate the pipeline", or similar
A feature or bugfix is complete and ready to push
Before creating a pull request
The user explicitly requests local validation before pushing

When NOT to use

In the middle of active development across multiple commits — wait until the logical unit of work is done
On every individual commit in a multi-commit feature — run once at the end
When the user only asks you to commit (committing does not imply CI validation)
When the user explicitly says to skip local validation

What this does

hm run executes the project's CI pipeline locally inside Docker containers. It runs the same steps that would run on Harmont Cloud, but on your machine. This catches failures before they reach remote CI.

Procedure

Run hm run -k --logs from the project root (-k continues past failures so you see every broken step in one run; --logs streams full build logs for easier diagnosis)
If it exits 0 — pipeline passed. Inform the user and proceed with push if requested.
If it exits non-zero — pipeline failed. Read the output, diagnose ALL failures (not just the first), fix every issue, and re-run hm run -k --logs until it passes.
Only after local CI is green: push to remote. If the user wants cloud validation too, they can run hm run --backend cloud --logs or wait for the remote CI triggered by the push.

Important

hm run is the ONLY correct way to run this project's CI locally. Do NOT try to reverse-engineer pipeline steps by reading .hm/ files and running commands manually.
Do NOT commit, push, and wait for remote CI results as a way to "test" — always validate locally first.
Exit code 0 = pass, non-zero = fail. Exit code 130 = user cancelled (Ctrl-C).
If Docker is not running, hm run will fail. Tell the user to start Docker.

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

2mo ago First seen · 39 lines · 60 tokens per session scan A 63aa0057dc35

Subscribe to this mod's changes

validate-ci is a skill published in the GitHub repository harmont-dev/harmont-cli (21 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 545 once invoked, about $0.0002 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.

CI and CD Code Generation DevOps and cloud ai-agents build-automation cli continuous-integration

validate-ci next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
validate-ciharmont-dev/harmont-cli	Skill	21	3mo ago	Apache-2.0	A	60	Claude Code
critiquegoogle-gemini/gemini-cli	Skill	109k	yesterday	Apache-2.0	A	23	Gemini CLI
rea-ci-tests-auditmorluto/rea	Skill	435k	yesterday	MIT	A	47	Claude Code, Codex
dd-code-generationDataDog/pup	Skill	1.0k	yesterday	Apache-2.0	A	16	Claude Code
atmos-hookscloudposse/atmos	Skill	1.4k	yesterday	Apache-2.0	A	46	Claude Code
atmos-modernizationcloudposse/atmos	Skill	1.4k	yesterday	Apache-2.0	A	36	Claude Code
atmos-procloudposse/atmos	Skill	1.4k	yesterday	Apache-2.0	A	38	Claude Code

harmont-cli: Skill for Claude Code