agentmods.dev

create-trigger

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

A tool for creating Harness triggers, which automatically start pipelines when events occur. It supports events such as Git changes, scheduled times, new container images, and Helm chart updates.

In plain words
What is it for?
Use it to create webhook, cron-based, artifact, or manifest triggers in Harness. It generates the trigger YAML, creates the trigger through Harness, and verifies Git webhooks.
Why use it?
It removes the need to start certain builds by hand. You can define when a pipeline should run and add filters such as branches, payload data, schedules, or artifact paths.

Skill for Claude CodeCodex

not rated 102 1mo ago A scan 48 tokens original Apache-2.0
View the source file harness/harness-skills
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.

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

Made for: Claude Code, Codex.

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-skills/create-trigger.svg)](https://agentmods.dev/skills/harness/harness-skills/create-trigger)
Your own site
<a href="https://agentmods.dev/skills/harness/harness-skills/create-trigger"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/create-trigger.svg" alt="Measured on agentmods" 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. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00048 $0.01379
Opus 5 $0.00024 $0.00690
Sonnet 5 $0.00010 $0.00276
Haiku 4.5 $0.00005 $0.00138

Measured 4d ago against content hash 4fda52404037, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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

Copies of this mod

1 near-identical copy found in the catalogue:

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. 4d 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-skills (102 stars, last pushed 1mo 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. 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 CDDevOps and cloudagent-skillsagents
Related

Other skills, from other repositories

ci-security-scanning-with-strix

Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…

usestrix/strix · 140 tokens

desktop-principles

Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.

Jwuthri/Tracely-ai · 36 tokens

upgrading-golang

Upgrades Go version across the entire Chainloop codebase including source files, Docker images, CI/CD workflows, and documentation. Use when the user mentions upgrading Go, golang version, or updating Go compiler version.

chainloop-dev/chainloop · 48 tokens

python-canary-fix

Investigate and propose fixes for Python canary cron failures in the openinference repo. Use when the user mentions Python canary failures, Python cron failures, or when the auto-fix CI job reports Python instrumentation canary issues.

Arize-ai/openinference · 53 tokens

ci-fixer

CI failures - read error, minimal fix, verify.

sipyourdrink-ltd/bernstein · 15 tokens

infrastructure-setup

Provides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations. Use when: "настрой инфраструктуру", "измени CI/CD", "подготовь деплой", "настрой Docker", "собери release artifact", "настрой мониторинг"…

pavel-molyanov/molyanov-ai-dev · 113 tokens