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-skills --skill create-pipeline-v1git clone --depth 1 https://github.com/harness/harness-skillsWrote 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-skills/create-pipeline-v1)<a href="https://agentmods.dev/skills/harness/harness-skills/create-pipeline-v1"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/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-skills/create-pipeline-v1"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/create-pipeline-v1.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 37 Data is uploaded to cloud storage (S3 / GCS / Azure Blob). This may be a legitimate backup or exfiltration to an external bucket. Manual review is recommended.Fix: Verify the destination bucket is trusted and owned by you. Never upload credentials, secrets, or workspace contents to external or unverified cloud storage.
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 11d 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`) Copies of this mod
1 near-identical copy found in the catalogue:
- create-pipeline-v1 — 100% identical, 0 lines differ
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.
- 11d 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-skills (105 stars, last pushed 2d 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
secrets-management
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
airflow-dag-patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.