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/codagent-ai/agent-skills/fix-prnpx skills add Codagent-AI/agent-skills --skill fix-prgit clone --depth 1 https://github.com/Codagent-AI/agent-skillsWrote 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/codagent-ai/agent-skills/fix-pr)<a href="https://agentmods.dev/skills/codagent-ai/agent-skills/fix-pr"><img src="https://agentmods.dev/badge/skills/codagent-ai/agent-skills/fix-pr.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.00063 | $0.01955 |
| Opus 5 | $0.00032 | $0.00978 |
| Sonnet 5 | $0.00013 | $0.00391 |
| Haiku 4.5 | $0.00006 | $0.00196 |
Grade A, and why
fix-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 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codagent:fix-pr
Fix CI failures and review comments on the current branch's PR by dispatching a fixer subagent with all failure context, verifying the fix with the validator, and pushing.
Steps
-
Gather CI failure context
# Get PR details gh pr view --json number,url,headRefName,baseRefName # Get all CI check results gh pr checks --json name,state,bucket,linkFor each failed check (bucket =
fail):- Extract the GitHub Actions run ID from the
linkfield:- Pattern:
/actions/runs/(\d+)/
- Pattern:
- Fetch failed logs:
gh run view <run-id> --log-failed - Collect: check name, link, and log output
- Extract the GitHub Actions run ID from the
-
Gather review comment context
# Get repo info gh repo view --json owner,name # Get all reviews gh api "repos/{owner}/{repo}/pulls/{pr-number}/reviews?per_page=100" # Get unresolved inline review threads via GraphQL (includes resolution status) # IMPORTANT: Inline owner, repo, and PR number directly into the query. # Do NOT use GraphQL variables ($owner, $repo) — the $ signs get stripped by the shell. gh api graphql -f query=' query { repository(owner: "<owner>", name: "<repo>") { pullRequest(number: <pr-number>) { reviewThreads(first: 100) { nodes { id isResolved comments(first: 10) { nodes { id author { login } path line body } } } } } } } '- Filter reviews to latest state per reviewer
- Collect
CHANGES_REQUESTEDreviews: author, body - From the GraphQL result, collect only threads where
isResolvedisfalse: thread id, comment id, author, file path, line, body
-
Dispatch fixer subagent
Use the fixer prompt from the ## Fixer Subagent Prompt appendix below.
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 · 294 lines · 63 tokens per session scan A 2ba2c6d757e9
fix-pr is a skill published in the GitHub repository Codagent-AI/agent-skills (30 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 1,955 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-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…