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 agentmods add skills/jepegit/issue-flow/gh-cinpx skills add jepegit/issue-flow --skill gh-cigit clone --depth 1 https://github.com/jepegit/issue-flowWhat 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 | $0.00084 | $0.00600 |
| Opus 5 | $0.00042 | $0.00300 |
| Sonnet 5 | $0.00017 | $0.00120 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
gh-ci 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 2d 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.
What it actually says
gh-ci — wait on GitHub CI with gh
Teach agents the concrete gh commands for listing and watching CI.
Always pass --repo <owner/repo> (never rely on gh's cwd default).
Primary (PR-attached checks)
Prefer these when a pull request number is known (usual /iflow-close path):
# One-shot snapshot — exit 0 means green (or all pass / skipping)
gh pr checks <number> --repo <owner/repo>
# Wait until checks finish (or fail-fast on red)
gh pr checks <number> --repo <owner/repo> --watch --fail-fast
Budget: honour 15 minutes wall-clock for any
--watch (from [issueflow].checks_watch_minutes /
ISSUEFLOW_CHECKS_WATCH_MINUTES, default 15). gh has no max-duration flag —
the agent stops the watch when the cap hits.
Fallback (workflow runs)
When gh pr checks returns empty, cannot resolve checks, or there is no PR yet
but a workflow run id is known:
gh run list --repo <owner/repo> --limit 10
gh run watch <run-id> --repo <owner/repo>
Optional: gh run view <run-id> --repo <owner/repo> --log-failed after a red
run to surface failing job logs.
Semantics
| Result | Meaning | Agent action |
|---|---|---|
Exit 0 / all pass or skipping |
CI green | Proceed (merge, report green, etc.) |
Fail / --fail-fast |
CI red | Stop hands-off paths; report failing check/run URLs |
| Still pending past budget | Unknown | Do not hang; report pending and follow the calling skill (e.g. close yolo may fall back to --auto) |
Where this fits
/iflow-closeowns the merge / yolo watch-then-merge sequence; this skill is the shared cheatsheet for the CI commands themselves.- Design record:
.issueflows/04-designs-and-guides/gh-list-and-watch.md(issues #172, #220).
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.
- 2d ago First seen · 61 lines · 84 tokens per session scan A f866df53b7ec
gh-ci is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 20d ago), licensed MIT. It adds 84 tokens to every session and 600 once invoked, about $0.0004 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-31.
Other skills, from other repositories
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
dsh-web-pre-push-checks
Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
harness-setup
HAR: Project init, tool setup, agent config, memory setup, skill mirror sync. Trigger: setup, init, new project, CI/Codex setup, harness-mem, mirror. Do NOT load for: implementation, review, release, planning.
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/.