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 skills add ambient-code/platform --skill pr-fixergit clone --depth 1 https://github.com/ambient-code/platformWrote 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/ambient-code/platform/pr-fixer)<a href="https://agentmods.dev/skills/ambient-code/platform/pr-fixer"><img src="https://agentmods.dev/badge/skills/ambient-code/platform/pr-fixer/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/ambient-code/platform/pr-fixer"><img src="https://agentmods.dev/badge/skills/ambient-code/platform/pr-fixer.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.00078 | $0.01072 |
| Opus 5.5 | $0.00031 | $0.00429 |
| Sonnet 5.5 | $0.00016 | $0.00214 |
| Haiku 4.5 | $0.00008 | $0.00107 |
Grade A, and why
pr-fixer 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pr-fixer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Fixer Skill
Triggers the Amber Handler (amber-issue-handler.yml) to automatically fix a pull request. Posting @ambient-code on a PR triggers the fix prompt, which creates an ACP session that rebases the PR, evaluates reviewer comments (fixes valid issues, responds to invalid ones), runs lints and tests, and pushes the fixes.
Usage
/pr-fixer <pr-number>
The PR number is required. Example: /pr-fixer 1234
What It Does
-
Validate prerequisites
- Confirm
ghCLI is authenticated (gh auth status) - Detect the repo from the local git remote (
gh repo view --json nameWithOwner --jq .nameWithOwner)
- Confirm
-
Pre-flight PR check
- Check the PR exists and its state:
gh pr view <N> --repo <owner/repo> --json state,isCrossRepository --jq '{state, isCrossRepository}' gh pr viewreturns state in uppercase:OPEN,CLOSED, orMERGED. A non-zero exit code (with stderr error) means the PR does not exist.- If the exit code is non-zero: abort with "PR #N not found in <owner/repo>."
- If state is
CLOSEDorMERGED: abort with "PR #N is already . Nothing to fix." (use the actual uppercase value returned) - Only proceed if state is exactly
OPEN. - If PR is from a fork (
isCrossRepository: true), warn: "PR #N is from a fork. The Amber Handler skips fork PRs. Push the branch to the org repo and re-open the PR, or fix locally."
- Check the PR exists and its state:
-
Trigger the fix
gh pr comment <N> --repo <owner/repo> --body "@ambient-code" -
Locate the triggered run
- Wait a few seconds for the run to register
- Find it via:
gh run list --workflow=amber-issue-handler.yml --repo <owner/repo> --limit 5 --json databaseId,status,createdAt,event - Match the most recent
issue_comment-triggered run created after the comment
-
Print the run URL immediately so the user has it:
PR Fixer dispatched for PR #<N> Run: https://github.com/<owner/repo>/actions/runs/<run-id> PR: https://github.com/<owner/repo>/pull/<N> Monitoring in background — you'll be notified when it completes.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 83 lines · 78 tokens per session scan A 409e0519371f
pr-fixer is a skill published in the GitHub repository ambient-code/platform (131 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 1,072 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
triage
Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.
05-review
Reviews a change or a diff and says whether it is ready to ship, naming every problem with its fix. Use when the user wants a change checked before it ships. Not for fixing what the review finds, and not for auditing a whole codebase.
review
Use when operating as the Fabrik Review stage agent. This skill guides code review of an implementation, finding and fixing issues, and ensuring the PR is ready for human review.
review-comment
Use when operating as the Fabrik Review comment reviewer. This skill guides applying user decisions on review findings — fixing issues, dismissing false positives, or deferring items — then committing and pushing without signaling stage completion.
pr-gates
This skill should be used when the user asks to "open a PR", "prepare for review", "address review comments", "run gates", or "verify before pushing" in this repository. Enforces preflight/gate workflow, migration safety, and review-evidence closure.
pull-request-automation
Audits and improves the pull request workflow for a GitHub repository. Covers PR description templates, auto-labelling, CODEOWNERS, PR size checks, and branch protection rules. Invoked when the user asks to improve the PR process, set up PR automation, or add a PR template.