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/patrickserrano/lacquer/github-ci-fixnpx skills add patrickserrano/lacquer --skill github-ci-fixgit clone --depth 1 https://github.com/patrickserrano/lacquerWhat 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.00057 | $0.01461 |
| Opus 5 | $0.00028 | $0.00731 |
| Sonnet 5 | $0.00011 | $0.00292 |
| Haiku 4.5 | $0.00006 | $0.00146 |
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 yesterday.
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 — 148 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 |
| Check PR status | gh pr checks <pr> |
| 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
gh run view <run-id> --json conclusion --jq .conclusion # poll until done
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 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.
- yesterday First seen · 148 lines · 57 tokens per session scan A e872d67c2d61
github-ci-fix is a skill published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 1,461 once invoked, about $0.0003 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
install-mimi-remote
安装、配置、配对、迁移、升级、诊断、回滚或卸载 Mimi Remote；在 macOS 上安装和维护 Mimi Remote Mac 菜单栏 App / DMG，或通过 Homebrew、Linux user-systemd 部署 agentd；从源码构建 iPhone/iPad App；配置 Codex 主通道和可选 Claude Code 实验 Runtime。用户提出“安装 Mimi Remote”“安装或修复 Mac 菜单栏 App”“在 iPad/iPhone 上使用 Codex 或 Claude Code”“部署、迁移或修复 agentd”“升级、回滚、卸载 Mimi Remote”“构建 MimiRemote iOS…
install-mimi-remote
安装、配置、配对、迁移、升级、诊断、回滚或卸载 Mimi Remote；在 macOS 上安装和维护 Mimi Remote Mac 菜单栏 App / DMG，或通过 Homebrew、Linux user-systemd 部署 agentd；从源码构建 iPhone/iPad App；配置 Codex 主通道和可选 Claude Code 实验 Runtime。用户提出“安装 Mimi Remote”“安装或修复 Mac 菜单栏 App”“在 iPad/iPhone 上使用 Codex 或 Claude Code”“部署、迁移或修复 agentd”“升级、回滚、卸载 Mimi Remote”“构建 MimiRemote iOS…
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
pinchtab-stealth-score
Run the PinchTab stealth-score sweep against 15 bot-detection / fingerprint sites (sannysoft, rebrowser, deviceandbrowserinfo, iphey, whoer, browserscan, pixelscan, fingerprint-scan, incolumitas, fvision, amiunique, browserleaks, creepjs, coveryourtracks, fingerprint-demo). Starts a Docker PinchTab container per…
api-server-mcp
REST API server and MCP protocol integration.