Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rjmurillo/ai-agents/plugin install project-toolkitWrote 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/commands/rjmurillo/ai-agents/pr-autofix)<a href="https://agentmods.dev/commands/rjmurillo/ai-agents/pr-autofix"><img src="https://agentmods.dev/badge/commands/rjmurillo/ai-agents/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.1 | $0.00039 | $0.19429 |
| Opus 5 | $0.00019 | $0.09714 |
| Sonnet 5 | $0.00008 | $0.03886 |
| Haiku 4.5 | $0.00004 | $0.01943 |
Grade C, and why
pr-autofix scanned grade C with 1 finding 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 2d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- # taste-lint: ignore file-size, this command is one end-to-end PR workflow; splitting it would hide required lease and mutation gates from the agent. --> How it starts
The opening of the file, as written. The whole thing — 1,285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pr-autofix
Autonomous PR monitor and fixer. This file carries the whole protocol, including the Ready-to-Merge definition below. Two bundled dependencies are required beyond it, both from the github skill: Phase 0 runs its transport preflight, and MCP mode reads its routing reference. Everything else needed to run the command is here.
Triggers
| Trigger phrase | Operation |
|---|---|
pr-autofix |
Triage all open PRs by tier and act |
autofix this pr |
Single-PR mode on the current branch's open PR |
monitor open prs |
Periodic triage without merging |
auto-merge ready prs |
Tier 1 only: enable auto-merge on land-ready PRs |
address pr feedback |
Tier 3/4 only: walk thread lifecycle |
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.
- 2d ago Changed · +15 lines 85ee3b6d52ed
- 4d ago Changed · +342 lines 5f78b9f71490
- 8d ago First seen · 928 lines · 39 tokens per session scan C ade1e7c96f48
pr-autofix is a command published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 19,429 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
sdlc-ship
Phase 4 — Ship. Runs devops-engineer for CI/CD, cloud deploy, and release. Reads verify-handoff.md for clean context.
pr
Create a pull request from the current branch.
cp
Stage, commit, and push the current branch following git governance rules.
portfolio-status
Review the health of all projects in the portfolio.
prune-source
Guided removal of a source store from sources/supported-stores.json — coherence check first, comment-out for one cycle, then delete.
checklist
Generate a custom checklist for the current feature based on user requirements.