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 PostHog/posthog-foss --skill triaging-merge-queue-failuresgit clone --depth 1 https://github.com/PostHog/posthog-fossWrote 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/posthog/posthog-foss/triaging-merge-queue-failures)<a href="https://agentmods.dev/skills/posthog/posthog-foss/triaging-merge-queue-failures"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/triaging-merge-queue-failures/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/posthog/posthog-foss/triaging-merge-queue-failures"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/triaging-merge-queue-failures.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Excessive Agency · line 89 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Data Exfiltration · line 97 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00180 | $0.09181 |
| Opus 5.5 | $0.00072 | $0.03672 |
| Sonnet 5.5 | $0.00036 | $0.01836 |
| Haiku 4.5 | $0.00018 | $0.00918 |
Grade A, and why
triaging-merge-queue-failures 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 12d 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.
- **`gh` is not installed.** Both helpers fall back to `curl` with `$GITHUB_TOKEN` and page by hand, so prefer them for everything they cover — reads, and the requeue comment. For anything else, either use `curl` against How it starts
The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triaging merge queue failures
One triage is one PR plus its latest Trunk queue attempt: establish the facts, walk the decision chart below, and end with a verdict and its action. Runs are either interactive (a developer asked about a kicked PR) or unattended (a scheduled sweep over recent kicks); the chart is identical, only the actions you may take yourself differ.
/merging-prs covers enqueueing and babysitting; this skill starts where it hands off, at a failed or removed queue entry.
How Trunk reports queue state here
Read this before writing any command. It is the part that goes stale.
Trunk publishes no check run in this repository. The trunk-io app posts zero check runs — not on the PR head, not on the queue branch. A predicate like select(.name | startswith("Trunk Merge Queue")) matches nothing, and a sweep built on it reports zero verdicts forever while the queue runs normally. /merging-prs, /debugging-ci-failures and AGENTS.md used to assert that check run exists; all three now point at trunk merge status instead.
Trunk exposes queue state three ways. Only the first carries Trunk's own reasons; the other two are what the GitHub API can see, and they are what this skill's helpers read:
trunk merge status <n>(the CLI) — the full state machine with a reason per transition, in Trunk's words. This is the primary source for why, and the only one that surfaces conflicts, line-skips and cancellations at all. Human text only, no--json. The same timeline is exportable as JSON from the Trunk dashboard.- One sticky comment per PR, authored by
trunk-io[bot], rewritten in place as state changes. It carries the current state, the failing check's name, and a link to the failing job. Rewritten means no history: earlier reasons are gone. It can also carry aFailed Test | Failure Summary | Logstable naming the failing test outright — check it before reading any log, and note it is empty for suites that do not upload results to Trunk. - One draft shadow PR per queue attempt, authored by
trunk-io[bot], with head reftrunk-merge/pr-<n>/<uuid>. Its head SHA carries the attempt's real CI as ordinarygithub-actionscheck runs, with job links. A-bisectionsuffix means Trunk is bisecting a failed batch to find the culprit.
What ships with it
4 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.
- 12d ago Changed f9aa622f1707
- 18d ago Changed aebb40e6b97e
- 1mo ago Changed · +2 lines b583c9a53524
- 1mo ago Changed 5f0a8036d8b8
- 1mo ago Changed · +29 lines b11f097b93e2
- 1mo ago Changed · +14 lines 15107d9b6966
- 1mo ago Changed · +60 lines · +9 tokens per session 37de165a81a8
- 1mo ago First seen · 205 lines · 171 tokens per session scan A 5a1cf0219b20
triaging-merge-queue-failures is a skill published in the GitHub repository PostHog/posthog-foss (726 stars, last pushed today), licensed MIT. It adds 180 tokens to every session and 9,181 once invoked, about $0.0007 per session on Opus 5.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-09-03.
Other skills, from other repositories
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
enable-check-includes-strict
Enable and migrate Chromium targets and directories to checkincludesstrict = true, diagnosing and resolving header include violations as part of the checkincludesstrict LSC. Use when adding directories to the allowlist, enabling strict header checks on targets, or resolving CHECKINCLUDESSTRICTUNTRIAGED targets.
resolve-handoff
Emit the complete Resolve handoff with exact modes, outcomes, test evidence, and publication state.
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.
cy-orquestrate-issue
Orchestrate GitHub bug resolution through a new CompozyOS managed worktree and Claude Opus 5.5 Medium session per issue. Investigate reported bugs, create missing issues, and dispatch an executor responsible for a detailed PR, green CI, and all CodeRabbit and Greptile feedback. Use when asked to delegate issue…