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 chhoumann/t3-pstack --skill fix-cigit clone --depth 1 https://github.com/chhoumann/t3-pstackWrote 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/chhoumann/t3-pstack/fix-ci)<a href="https://agentmods.dev/skills/chhoumann/t3-pstack/fix-ci"><img src="https://agentmods.dev/badge/skills/chhoumann/t3-pstack/fix-ci/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/chhoumann/t3-pstack/fix-ci"><img src="https://agentmods.dev/badge/skills/chhoumann/t3-pstack/fix-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00019 | $0.00203 |
| Opus 5.5 | $0.00008 | $0.00081 |
| Sonnet 5.5 | $0.00004 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
fix-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 3d 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.
This is a copy
86% identical to fix-ci — 0 lines 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.
What it actually says
Fix CI
Trigger
Branch or PR CI is failing and needs a fast, iterative path to green checks.
Workflow
- Resolve the active PR and inspect
gh pr checks --json name,bucket,state,workflow,link. - Inspect failed jobs and extract the first actionable error. Use GitHub Actions logs when available; otherwise use the check link to identify the failing command or service.
- Apply the smallest safe fix.
- Push, re-check the PR check set, and repeat until green.
Guardrails
- Fix one actionable failure at a time.
- Prefer minimal, low-risk changes before broader refactors.
- Keep
gh pr checksas the source of truth for overall PR CI state.
Output
- Primary failing job and root error
- Fixes applied in iteration order
- Current CI status and next action
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.
- 3d ago First seen · 30 lines · 19 tokens per session scan A 925f8c3e11de
fix-ci is a skill published in the GitHub repository chhoumann/t3-pstack (190 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 203 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to fix-ci, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
repair-github-ci
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time, or missing outputs after a cache hit. Also covers pipeline hangs, tasks…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
meta-long-running-build-watchdog
Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.
tracely
Instrument AI agents with Tracely and turn their production traces into CI gates. Use when the user mentions Tracely, tracely-ai, tracelysdk, the tracely CLI, or asks to trace/observe an AI agent, add LLM evaluators or LLM-as-a-judge columns, debug why a trace or conversation isn't showing up, wire agent regression…