create-trigger

create-trigger is a skill for Claude Code from harness/harness-ai. It costs 48 tokens per session (1,379 once invoked), scanned A, a copy of create-trigger, Apache-2.0.

A tool for creating Harness triggers, which automatically start a software pipeline when an event occurs. A pipeline is an automated sequence that builds, tests, or deploys software.

In plain words
What is it for?
Use it to create webhook, scheduled, artifact, or manifest triggers, add filters such as branches or payload conditions, and verify Git webhook registration.
Why use it?
It turns requirements such as a Git event, schedule, new registry artifact, or Helm change into a trigger configuration and creates it in Harness.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the harness plugin — 56 skills, 1 MCP server shipped together

Good fit Use it to create webhook, scheduled, artifact, or manifest triggers, add filters such as branches or payload conditions, and verify Git webhook registration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/harness/harness-ai/create-trigger
Install

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.

Any agent
npx skills add harness/harness-ai --skill create-trigger
Clone the repo
git clone --depth 1 https://github.com/harness/harness-ai

Made for: Claude Code.

Or install harness, the plugin that ships this one along with the rest of its 56 skills, 1 MCP server.

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 create-trigger

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/harness/harness-ai/create-trigger"><img src="https://agentmods.dev/badge/skills/harness/harness-ai/create-trigger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,379 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 100% copy Near-identical to another mod 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.00048 $0.01379
Opus 5.5 $0.00019 $0.00552
Sonnet 5.5 $0.00010 $0.00276
Haiku 4.5 $0.00005 $0.00138

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

Security

Grade A, and why

create-trigger 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.

Origin

This is a copy

100% identical to create-trigger — 1 line 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.

plugins/claude/skills/create-trigger/SKILL.md · 227 lines

How it starts

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

Create Trigger

Generate Harness Trigger YAML and push to Harness via MCP.

Instructions

  1. Identify trigger type - Webhook (Git events), Scheduled (cron), Artifact (registry updates), or Manifest (Helm chart updates)
  2. Configure conditions - Branch filters, payload conditions, cron expression, or artifact path
  3. Generate YAML using the templates below, referencing the target pipeline
  4. Create via MCP using harness_create with resource_type trigger
  5. Verify webhook registration - For webhook triggers, confirm the webhook is registered in the Git provider

Trigger Types

  • Webhook - GitHub, GitLab, Bitbucket, Azure Repos, Custom
  • Scheduled - Cron-based scheduling
  • Artifact - Docker Hub, ECR, GCR, ACR, Nexus
  • Manifest - Helm chart updates

Webhook Trigger (GitHub)

trigger:
  name: PR Trigger
  identifier: pr_trigger
  orgIdentifier: default
  projectIdentifier: my_project
  pipelineIdentifier: ci_pipeline
  source:
    type: Webhook
    spec:
      type: Github
      spec:
        type: PullRequest
        spec:
          connectorRef: github_connector
          autoAbortPreviousExecutions: true
          payloadConditions:
            - key: targetBranch
              operator: Equals
              value: main
          headerConditions: []
          jexlCondition: ""
          actions:
            - Open
            - Reopen
            - Synchronize
  inputYaml: |
    pipeline:
      identifier: ci_pipeline
      properties:
        ci:
          codebase:
            build:
              type: PR
              spec:
                number: <+trigger.prNumber>

GitHub Event Types

  • Push - Code pushed to branch
  • PullRequest - PR events (Open, Close, Reopen, Synchronize, Edit)
  • IssueComment - PR comments (Create, Edit, Delete)
  • Release - Release events (Create, Publish, Edit)

Webhook Trigger (GitLab)

trigger:
  name: GitLab Push
  identifier: gitlab_push
  pipelineIdentifier: ci_pipeline
  source:
    type: Webhook
    spec:
      type: Gitlab
      spec:
        type: Push
        spec:
          connectorRef: gitlab_connector
          payloadConditions:
            - key: ref
              operator: Contains
              value: main

Read the full file on GitHub · 227 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 · 227 lines · 48 tokens per session scan A 4fda52404037

Subscribe to this mod's changes

create-trigger is a skill published in the GitHub repository harness/harness-ai (27 stars, last pushed 4d ago), licensed Apache-2.0. It adds 48 tokens to every session and 1,379 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to create-trigger, differing in 1 line, and is treated as a copy.

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