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 skills add harness/harness-ai --skill create-pipeline-v1git clone --depth 1 https://github.com/harness/harness-aiWrote 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.
[](https://agentmods.dev/skills/harness/harness-ai/create-pipeline-v1)<a href="https://agentmods.dev/skills/harness/harness-ai/create-pipeline-v1"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/create-pipeline-v1/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.
<a href="https://agentmods.dev/skills/harness/harness-ai/create-pipeline-v1"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/create-pipeline-v1.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00148 | $0.03288 |
| Opus 5 | $0.00074 | $0.01644 |
| Sonnet 5 | $0.00030 | $0.00658 |
| Haiku 4.5 | $0.00015 | $0.00329 |
Grade A, and why
create-pipeline-v1 scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Ticketing → use `action: uses: jira-create` / `snow-create` (never `run: curl`) This is a copy
100% identical to create-pipeline-v1 — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pipeline v1
Generate Harness v1 simplified Pipeline YAML and optionally push to Harness via MCP.
Alpha: This skill is currently in internal testing only.
Instructions
- Confirm v1 format - User must specifically want v1 syntax. Default to v0 (
/create-pipeline) if unclear. - Clarify requirements - Pipeline type (CI, CD, or both), language/framework, deployment target
- Consult the spec reference - Use
references/v1-spec-schema.mdfor the complete v1 schema, step types, action catalog, and examples - Select native actions - Always prefer native action and template steps over
run:steps. Consultreferences/native-actions.mdfor the full mapping. Key rules:- Docker build/push → use
template: uses: buildAndPushToDocker/buildAndPushToECR/buildAndPushToGAR(neverrun: docker build && docker push) - K8s deploy → use
action: uses: kubernetes-rolling-deployortemplate: uses: k8sRollingDeployStep(neverrun: kubectl apply) - Helm deploy → use
action: uses: helm-deployortemplate: uses: helmDeployBasicStep(neverrun: helm upgrade --install) - ECS deploy → use
template: uses: ecsBluegreenDeployStep(neverrun: aws ecs update-service) - Terraform → use
template: uses: terraformStep(neverrun: terraform apply) - Security scanning → use native STO templates (
gitleaksStep,banditStep,sbomOrchestrationStep) - Uploads → use
template: uses: uploadArtifactsToS3/uploadArtifactsToGCS(neverrun: aws s3 cp) - Approvals → use
approval: uses: harnessorapproval: uses: jira(never polling scripts) - Ticketing → use
action: uses: jira-create/snow-create(neverrun: curl) - HTTP requests → use
action: uses: httportemplate: uses: httpStep(neverrun: curl) - Use
run:steps only for custom build/test/lint commands with no native equivalent
- Docker build/push → use
- Generate v1 YAML using flat structure,
${{ }}expressions,scriptfield for run steps, andaction/templatesteps for deployments - Optionally create via MCP using
harness_createwith resource_typepipeline
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 484 lines · 148 tokens per session scan A 278f0723074b
create-pipeline-v1 is a skill published in the GitHub repository harness/harness-ai (19 stars, last pushed 19d ago), licensed Apache-2.0. It adds 148 tokens to every session and 3,288 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to create-pipeline-v1, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
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.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
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.
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.