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.
npx agentmods add skills/harmont-dev/harmont-cli/convert-ghanpx skills add harmont-dev/harmont-cli --skill convert-ghagit clone --depth 1 https://github.com/harmont-dev/harmont-cliWhat 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 | $0.00068 | $0.01600 |
| Opus 5 | $0.00034 | $0.00800 |
| Sonnet 5 | $0.00014 | $0.00320 |
| Haiku 4.5 | $0.00007 | $0.00160 |
Grade A, and why
convert-gha 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Convert existing GitHub Actions workflows (.github/workflows/*.yml / *.yaml) into Harmont CI pipelines. This skill reads your GHA configuration, explains what maps directly and what changes, then uses the write-pipeline skill to produce the Harmont pipeline.
When to use
- The user asks to "convert", "migrate", or "port" their GitHub Actions to Harmont
- The user says "I have GHA workflows" and wants Harmont equivalents
- The user asks "how do I replace GitHub Actions with Harmont"
hm inittold the user about this skill after detecting.github/workflows/
When NOT to use
- The user wants to write a Harmont pipeline from scratch — use the
write-pipelineskill directly - The user wants to keep using GitHub Actions alongside Harmont (dual CI setup)
- The user is debugging an existing Harmont pipeline — use the
validate-ciskill
Before you start
-
Read every workflow file in
.github/workflows/:find .github/workflows -name '*.yml' -o -name '*.yaml' | sortRead each file. Understand what each workflow does, what triggers it, and what its jobs and steps accomplish.
-
Fetch the Harmont patterns guide — required before writing anything:
WebFetch https://docs.harmont.dev/pipeline-sdk/patterns.md
Procedure
-
Inventory the GHA workflows. For each
.ymlfile, note:- Workflow name and trigger events (
on: push,on: pull_request, etc.; note anyon: schedule— see the mapping table for why scheduled triggers don't map to a local pipeline) - Each job: its name,
runs-on, and what it does - Dependencies between jobs (
needs:) - Services used (
services:) - Secrets and environment variables referenced
- Caching steps (
actions/cache,actions/setup-*with built-in caching) - Artifacts (
actions/upload-artifact,actions/download-artifact) - Matrix strategies
- Workflow name and trigger events (
-
Map GHA concepts to Harmont. Present the user with a summary table covering what they have and how it translates:
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.
- 2d ago First seen · 97 lines · 68 tokens per session scan A 8600382676d4
convert-gha is a skill published in the GitHub repository harmont-dev/harmont-cli (21 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,600 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
zuke-write-build
Write or edit a Zuke build (zuke.ts) — the code-first, strongly-typed build system for Deno/TypeScript. Use when adding or changing targets, wiring dependencies, calling a tool wrapper (DenoTasks, NpmTasks, DockerTasks, ...), generating CI, or authoring/refactoring a zuke.ts build file. For first-time project…
zuke-setup
Set up Zuke — a code-first, strongly-typed build automation system for Deno/TypeScript — in a project. Use when the user wants to add Zuke to a repo, scaffold a zuke.ts build file, install the Zuke CLI, or bootstrap the ./zuke launcher. After scaffolding, switch to the zuke-write-build skill to author targets.
ci-secure
Scans a repo's GitHub Actions workflows for the ten critical CI/CD attack vectors — template injection, fork code executed with privileges (pwn requests), cache poisoning, impostor action SHAs, secrets dumps, GITHUBENV hijack, write-token untrusted triggers, credentials in caches/artifacts, unverified remote code…
skills-registry-security
Checks the third-party security audit status of a skill published to a skills registry (skills.sh) across every cached surface, decides whether a failing finding is real or points at content already removed, and drives a stale badge to green unattended. Runs a real install to capture what users see, reads the…
sling
Diagnoses GitHub Actions failures and attributes CI time and cost using StarSling's sling CLI. Invoke this BEFORE using gh or fetching any logs whenever the user asks why a job or run failed, what made a run slow, about runner minutes or CI cost, asks to re-run or cancel a run, or pastes a GitHub Actions URL — sling…
ci-score
Grades a repository's GitHub Actions configuration against CI best practices (the CI Score: eleven pass/fail configuration facts computed from the repo's own workflow YAML) and hands back concrete fixes for every gap, ranked by impact and risk, each with an apply-now option and a paste-able agent prompt. Use when: (1)…