Borrowing it
Nothing to install: this file belongs to Fighter90/career-ops-ui. 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/Fighter90/career-ops-ui/main/.claude/skills/contributor-pr/SKILL.mdgit clone --depth 1 https://github.com/Fighter90/career-ops-uiWrote 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/fighter90/career-ops-ui/contributor-pr)<a href="https://agentmods.dev/skills/fighter90/career-ops-ui/contributor-pr"><img src="https://agentmods.dev/badge/skills/fighter90/career-ops-ui/contributor-pr/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/fighter90/career-ops-ui/contributor-pr"><img src="https://agentmods.dev/badge/skills/fighter90/career-ops-ui/contributor-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.01349 |
| Opus 5.5 | $0.00026 | $0.00540 |
| Sonnet 5.5 | $0.00013 | $0.00270 |
| Haiku 4.5 | $0.00006 | $0.00135 |
Grade A, and why
contributor-pr 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 1mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
contributor-pr — external PR intake pipeline
Proven on v1.125.2 (PRs #144/#145 by @Alien10140 — Gemini defaults + the headless deep-prompt 502 fix). External code gets a stricter path than our own branches: fork CI does not auto-run, review claims are verified empirically, and merges need explicit user authorization.
Phase 1 — Review (local runs ARE the CI gate)
- Fork PRs from first-time contributors show "no checks reported" —
GitHub Actions waits for maintainer approval. Don't chase it; the local
full-suite run below substitutes, and push-CI on main re-validates after
merge. (Approving runs via
gh api …/actions/runs/<id>/approveandgh pr mergeare both classifier-blocked for external PRs — when blocked, STOP and hand the user the exact commands; never work around.) git fetch origin pull/<n>/head:pr-<n>and read the FULL diff. Extra scrutiny on LLM surfaces (prompts.mjs,routes/llm.mjs), sanitizers, any new ingress, and i18n snapshot regeneration (dup keys / glosses). Check the contributor's tests honor CI isolation (dynamic imports inbefore(),CAREER_OPS_ROOTmktemp — the paths-once rule).- Verify factual claims against live sources, never training data.
v1.125.2 lesson: an AI review called
gemini-3.6-flash"fabricated" as a BLOCKER; fetching https://ai.google.dev/gemini-api/docs/models proved the contributor right (3.6-flash Stable, 2.0-flash shut down). Model ids, API shapes, deprecations → WebFetch the official docs. - Run the full suite on EACH pr-branch:
npm test, capture the exit code directly (never pipe to grep). Record per-branch counts. - Before merging, re-check
gh pr view <n> --json headRefOidstill equals the SHA you reviewed.
Phase 2 — Merge
- Needs the user's explicit go for THESE PRs (standing "merge all branches" does not auto-extend to external code; the classifier enforces this).
gh pr merge <n> --squash --delete-branch, oldest first; thengit checkout mainas its OWN command, thengit pull(a checkout inside a blocked compound command silently never runs; v1.125.2: a README commit landed on the local pr-144 branch that way and had to be cherry-picked to main).- Full suite on merged main.
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.
- 1mo ago First seen · 93 lines · 65 tokens per session scan A b2770d6232eb
contributor-pr is a skill published in the GitHub repository Fighter90/career-ops-ui (88 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 1,349 once invoked, about $0.0003 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-30.
Other skills, from other repositories
pull-request
Use this whenever the user asks to "open a PR", "ship this", "create the pull request", "make a PR", or once a feature/fix is verified and ready to push. Full lifecycle: branch → commit (commitizen) → issue → draft PR → CI → ready → autonomous monitor loop (fix comments, resolve threads, iterate until CI green + zero…
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
otto-drive-pr
PR mergeability, CI, and live preview.
voicestudio-maintainer
Triage GitHub issues, review contributor pull requests, diagnose CI, and prepare explicitly requested releases for VoiceStudio's Electron desktop app and Python backend. Use for repository maintenance work, not ordinary VoiceStudio audio generation.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…