github-actions-trigger-gotchas

github-actions-trigger-gotchas is a skill for Claude Code, Codex from AmineDjeghri/personal-os-setup. It costs 20 tokens per session (929 once invoked), scanned A, original, MIT.

A troubleshooting guide for GitHub Actions triggers and schedules. GitHub Actions is GitHub's system for running automated jobs, such as tests, when repository events occur.

In plain words
What is it for?
Use it to inspect workflow runs, jobs, steps, pull-request checks, branch protection, and rulesets before changing workflow configuration.
Why use it?
It helps explain why jobs run unexpectedly, fail to run, run twice, or get cancelled by concurrency settings.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inspect workflow runs, jobs, steps, pull-request checks, branch protection, and rulesets before changing workflow configuration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aminedjeghri/personal-os-setup/github-actions-trigger-gotchas
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 AmineDjeghri/personal-os-setup --skill github-actions-trigger-gotchas
Clone the repo
git clone --depth 1 https://github.com/AmineDjeghri/personal-os-setup

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 github-actions-trigger-gotchas

README.md
[![agentmods](https://agentmods.dev/badge/skills/aminedjeghri/personal-os-setup/github-actions-trigger-gotchas/github.svg)](https://agentmods.dev/skills/aminedjeghri/personal-os-setup/github-actions-trigger-gotchas)
Your own site
<a href="https://agentmods.dev/skills/aminedjeghri/personal-os-setup/github-actions-trigger-gotchas"><img src="https://agentmods.dev/badge/skills/aminedjeghri/personal-os-setup/github-actions-trigger-gotchas/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 github-actions-trigger-gotchas

Your own site · 80×15
<a href="https://agentmods.dev/skills/aminedjeghri/personal-os-setup/github-actions-trigger-gotchas"><img src="https://agentmods.dev/badge/skills/aminedjeghri/personal-os-setup/github-actions-trigger-gotchas.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 929 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 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.1 $0.00020 $0.00929
Opus 5.5 $0.00008 $0.00372
Sonnet 5.5 $0.00004 $0.00186
Haiku 4.5 $0.00002 $0.00093

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

Security

Grade A, and why

github-actions-trigger-gotchas 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 18d 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.

src/personal_os_setup/config/chezmoi/dot_claude/skills/github-actions-trigger-gotchas/SKILL.md · 64 lines

How it starts

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

GitHub Actions trigger & scheduling gotchas

False runs on Renovate/branch pushes, duplicated checks, jobs cancelled by concurrency, or a step that silently never executes. Diagnose with real evidence before editing YAML:

gh run list --branch <branch> --limit 20 --json workflowName,event,headBranch,createdAt,conclusion
gh api repos/O/R/actions/runs/<run-id>/jobs --jq '.jobs[]|"\(.name) \(.conclusion)"'
gh api repos/O/R/actions/runs/<run-id>/jobs --jq '.jobs[]|select(.name|test("X"))|.steps[]|"\(.number) \(.name) -> \(.conclusion)"'
gh pr checks <n>          # duplicate identical check names = two runs (push + pull_request)
gh api repos/O/R/branches/main/protection ; gh api repos/O/R/rulesets   # what actually gates merges

1. push + paths fires for unrelated diffs after a force-push

On a rebase/force-push (Renovate does this), GitHub evaluates the push path filter against everything the branch gained relative to its previous tip — including files main picked up since the branch was created. Symptom: an add-on CI fires on a renovate/* push whose PR only touches one unrelated folder; correlation is exact (only the folders added to main after the branch was cut fire).

Fix: scope the push trigger to the branch that matters (push: branches: [main]), keep validation on pull_request (whose paths uses the PR diff, correctly). Do not add paths-ignore hacks.

Same pattern causes double CI on every PR (push + pull_request both match). Pick one trigger — usually drop push unless a push without a PR must be validated. Check first whether protection/rulesets require those checks (often none).

2. Job-level concurrency cancels a run's OWN sibling jobs

jobs.<id>.concurrency with the default queue holds one running + one pending per group: each newly queued job cancels the pending one (cancel-in-progress: false only protects the running job). With N jobs starting together (cron, fan-out), all but ~2 get cancelled every run — worse than the race you were fixing. queue: max (up to 100 pending) fixes it, but an unsupported key invalidates the whole workflow file (all runs stop), so for a critical job prefer mechanisms with no new syntax.

Read the full file on GitHub · 64 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. 18d ago Changed · +3 lines 4f8f2ecf3dbf
  2. 27d ago First seen · 61 lines · 20 tokens per session scan A e2b5b04b1289

Subscribe to this mod's changes

github-actions-trigger-gotchas is a skill published in the GitHub repository AmineDjeghri/personal-os-setup (654 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 929 once invoked, about $0.0001 per session on Opus 5.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-09-19.