Borrowing it
Nothing to install: this file belongs to adamayoung/TMDb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adamayoung/TMDb/main/.claude/skills/fix-pr-checks/SKILL.mdgit clone --depth 1 https://github.com/adamayoung/TMDbWrote 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/adamayoung/tmdb/fix-pr-checks)<a href="https://agentmods.dev/skills/adamayoung/tmdb/fix-pr-checks"><img src="https://agentmods.dev/badge/skills/adamayoung/tmdb/fix-pr-checks/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/adamayoung/tmdb/fix-pr-checks"><img src="https://agentmods.dev/badge/skills/adamayoung/tmdb/fix-pr-checks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 43 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00094 | $0.03165 |
| Opus 5 | $0.00047 | $0.01582 |
| Sonnet 5 | $0.00019 | $0.00633 |
| Haiku 4.5 | $0.00009 | $0.00316 |
Grade A, and why
fix-pr-checks 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 10d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix PR Checks
Get a pull request's failing checks green: for each failing status check,
diagnose the cause, apply and verify a fix, and push. This is a single sweep
over the checks failing right now — it diagnoses and fixes them, pushes once,
and returns. Waiting on pending checks and deciding whether to sweep again belong
to the caller (you, or /watch-pr).
Repo is adamayoung/TMDb. GitHub reads use the GitHub MCP (mcp__github__*);
gh is authenticated and used for the blocking CI wait. If an MCP call fails with
401/403 (PAT expired or missing scope), fall back to the equivalent gh command.
It stands on the diagnosis skills
Don't read CI logs yourself. The analysis is already a capability — delegate it to
a Haiku subagent running the matching diagnosis skill (a repeat failure
re-diagnoses on Opus — see §2), so raw logs never enter your context and you
get back a file:line cause and a concrete fix:
- The Integration check (live-API suite from
integration.yml) →/diagnose-integration-failure - Any CI check — lint, markdown lint, build, or unit tests from
ci.yml→/diagnose-ci-failure
This skill is the act-on-it layer: route → fix → verify → commit → push.
Principles
- One sweep, then return. Handle every check failing at invocation, push once, report. Don't loop waiting for the re-run — that convergence is the caller's job.
- Diagnose via Haiku, escalate a repeat to Opus, fix locally. Get Cause/Fix from the diagnosis skill, then apply it and verify before claiming it fixed with the delegated build/test skills. First diagnosis of a check runs on Haiku; a check that comes back after a fix re-diagnoses on Opus (§2).
- Respect the attempt cap. A check gets at most 3 fix→push attempts (tracked in the run ledger). If it still fails on the same root cause, stop touching it and report it exhausted — never loop forever.
- Failing only. Act on
failchecks.pendingchecks are not yours to chase — report them and leave waiting to the caller.claude-reviewand other neutral checks are non-blocking. - Never fake green. Don't edit
.github/workflows/*or CI config to silence a check, and don't force-push, without surfacing to the user first.
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.
- 10d ago First seen · 256 lines · 94 tokens per session scan A b425b921a809
fix-pr-checks is a skill published in the GitHub repository adamayoung/TMDb (176 stars, last pushed 9d ago), licensed Apache-2.0. It adds 94 tokens to every session and 3,165 once invoked, about $0.0005 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-30.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
start-temps-cluster
Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.