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/tellahq/opensession/pr-autofixnpx skills add tellahq/opensession --skill pr-autofixgit clone --depth 1 https://github.com/tellahq/opensessionWrote 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/tellahq/opensession/pr-autofix)<a href="https://agentmods.dev/skills/tellahq/opensession/pr-autofix"><img src="https://agentmods.dev/badge/skills/tellahq/opensession/pr-autofix.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.01268 |
| Opus 5 | $0.00016 | $0.00634 |
| Sonnet 5 | $0.00006 | $0.00254 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
pr-autofix 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 4d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR auto-fix
Address ALL the open review feedback on a PR, from automated and human reviewers alike, plus any failing CI. Then commit, push, and reply in each thread you addressed. This is the methodology behind Open Session's os-auto-fix label loop; it also runs standalone from a session.
You are expected to fix everything actionable, not just blockers — P2 and P3 findings included. Only leave a finding unfixed when you have a clear reason, and record that reason (see the disposition lines at the end).
This skill is headless-safe: never use AskUserQuestion or any interactive tool.
Setup
If $ARGUMENTS contains a PR number, use it; otherwise use the current branch's PR. Resolve the repo with gh repo view --json owner,name (below, <repo> is that owner/name).
gh pr view <pr> --json number,title,headRefName,state,url
If the PR isn't OPEN, stop and say so.
Gather the work
The caller may have already listed the open review feedback and failing CI checks in its prompt — treat that as current and don't re-derive it. Otherwise gather it yourself:
- Inline review comments:
gh api repos/<repo>/pulls/<pr>/comments— skip outdated ones (no currentline). - Review summaries:
gh api repos/<repo>/pulls/<pr>/reviews(every reviewer, not just bots). - Conversation:
gh pr view <pr> --comments— humans sometimes put requests there. - CI:
gh pr checks <pr>; for failures, read the logs and reproduce locally (run the relevant tests/typecheck/lint).
Then read the diff (gh pr diff <pr>) and enough surrounding code to understand each finding in context.
Scope governor
Review feedback is not permission to grow the PR. Before fixing each finding, classify it:
- In-scope — introduced or made worse by this PR's diff, and fixable without changing what the PR is about. Fix it.
- Follow-up — real, but pre-existing behavior, an adjacent surface, or cleanup beyond this change. Leave the code unchanged, reply in the thread proposing the follow-up (no fixed-marker), and record it on SKIPPED as "finding — out of scope, follow-up".
- Out-of-scope — needs a new API/protocol/config/storage contract, a migration, or a design decision this PR never made. Same treatment as follow-up: propose, don't implement.
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.
- 4d ago First seen · 75 lines · 32 tokens per session scan A 671f41ad2788
pr-autofix is a skill published in the GitHub repository tellahq/opensession (345 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,268 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…