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 patrickserrano/lacquer --skill github-ci-fixgit clone --depth 1 https://github.com/patrickserrano/lacquerWrote 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/patrickserrano/lacquer/github-ci-fix)<a href="https://agentmods.dev/skills/patrickserrano/lacquer/github-ci-fix"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/github-ci-fix/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/patrickserrano/lacquer/github-ci-fix"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/github-ci-fix.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.00027 | $0.01975 |
| Opus 5.5 | $0.00011 | $0.00790 |
| Sonnet 5.5 | $0.00005 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00198 |
Grade A, and why
github-ci-fix 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 23d 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub CI Fix
Overview
Systematic workflow for debugging failing PR checks using gh CLI. Identifies GitHub Actions failures with logs, scopes external checks (Buildkite, etc.) as out-of-scope, then uses existing plan workflow for fixes.
Prerequisites
gh auth status # Required scopes: repo, workflow
STOP if unauthenticated: gh auth login --scopes repo,workflow
Quick Reference
| Task | Command |
|---|---|
| Find current PR | gh pr view --json number,url |
| Inspect PR status (snapshot only) | gh pr checks <pr> |
| Wait for CI | lacquer wait pr <N> |
| View run details | gh run view <run-id> |
| Get failed logs | gh run view <run-id> --log-failed |
| Full run log | gh run view <run-id> --log |
| Recent runs for this check | gh run list --workflow <name> --branch <branch> --json conclusion,headSha,createdAt -L 20 |
| Rerun without code changes (flakiness probe) | gh run rerun <run-id> --failed |
Workflow
1. Verify Auth → 2. Find PR → 3. Inspect
gh auth status # If fails: ask user to authenticate
gh pr view --json number,url # Or use user-provided PR number
gh pr checks <pr> # Shows check name, status, details URL
4. Scope: GitHub Actions vs External
GitHub Actions (detailsUrl has /actions/runs/): Pull logs, extract snippets, fix
External CI (Buildkite, CircleCI): Report URL only, request user to share logs
STOP: Do not attempt external CI log access.
4.5. Flaky or Real? Scope the Breaking Commit
Before treating a failure as a bug to fix, rule out flakiness — a fix for a flaky test is a wasted diagnosis, and a "fix" that just happens to make a flaky test pass on the next run isn't actually verified.
Flakiness probe:
gh run rerun <run-id> --failed # same commit, no code change
lacquer wait pr <N> # Wait for the rerun, then inspect its outcome
If it now passes with nothing changed, it's flaky — report that (test name, run URL, "passed on rerun with no changes") rather than diagnosing a bug that isn't there. Don't silently move on either: a flaky check is still worth flagging to the user, since it can mask a real failure next time.
What ships with it
1 file 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.
- 23d ago Changed · +36 lines · -30 tokens per session 26cec0d63ecf
- 1mo ago First seen · 148 lines · 57 tokens per session scan A e872d67c2d61
github-ci-fix is a skill published in the GitHub repository patrickserrano/lacquer (4 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 1,975 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-08-31.
Other skills, from other repositories
printing-press-polish
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use…
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…
atmos-lint
Atmos Terraform linting with TFLint: standalone atmos terraform lint, component-aware config discovery and toolchain versions, TFLint rule configuration, and lifecycle hooks/CI findings. Use when configuring, running, debugging, or documenting Terraform/OpenTofu linting in an Atmos project.
pi-loop-forensics
Diagnose pi-go agent loops and degenerate turns — "agent loop aborted", runaway thinking with no tool calls, repeated phrases. Discriminates genuine model repetition collapse from a race, a tool-parse failure, or a too-low guard, and A/B replays a seed session across providers.
nightly-session-watch
Nightly sweep of the last 24h of pi-go sessions — anomalous runs, loop aborts, tool error rates, token waste, real prompt-token spend, and whether the observation and palace pipelines are still recording. Triages each finding to the specialist skill that diagnoses it. Use for an unattended daily health check, or on…