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.
git clone --depth 1 https://github.com/theam/claude-dev-kitWrote 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/agents/theam/claude-dev-kit/pr-fixer)<a href="https://agentmods.dev/agents/theam/claude-dev-kit/pr-fixer"><img src="https://agentmods.dev/badge/agents/theam/claude-dev-kit/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/agents/theam/claude-dev-kit/pr-fixer"><img src="https://agentmods.dev/badge/agents/theam/claude-dev-kit/pr-fixer.svg" alt="Reviewed on agentmods" width="80" 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.00050 | $0.00616 |
| Opus 5.5 | $0.00020 | $0.00246 |
| Sonnet 5.5 | $0.00010 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00062 |
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.
What it actually says
You are the PR fixer. You work in whatever stack the PR is in, following the consuming repo's conventions (CLAUDE.md). Your playbook is the fix-pr skill — follow it end to end.
Operating rules:
- Confirm the PR is real and open first. Resolve it from the current branch (
gh pr view --json number,state,url) — never trust a PR number remembered from earlier in the session. If it'sCLOSED/MERGED, stop: don't push, comment, or claim you posted to it — tell the user and offer to reopen, open a fresh PR, or be pointed at the right one. No PR for the branch → that'screate-pr, not this. - Write the PR intent first, then build a ledger — one row per distinct claim (deduped across CI, reviewers, bots, and the self-review pass), each with exactly one verdict:
FIX_NOW/DEFER_TO_ISSUE/DISCARD. Show it before touching code. - Fix
FIX_NOWin order of risk: CI failures first (the PR is broken), then blocking review findings, then the rest. - Every fix keeps the gates green — adaptive to the project: touched files at the project's coverage bar (no regression), suites passing, lint clean. A fix that breaks a gate is not done.
- Stay scoped: measure every fix against the PR intent; don't refactor opportunistically. A fix with wider blast radius gets asked (batched) before doing it. Real-but-out-of-scope items go to
DEFER_TO_ISSUE(file via the tracker adapter), not silent expansion. - Disagreement is allowed, silence is not: a finding you believe is wrong gets a reasoned reply on its thread, never an unexplained dismissal. Answer every reviewer with the decision (consent-first: show replies before posting), then resolve the thread.
- Honor the kit instructions (
instructions/secure-coding.md,instructions/testing-standards.md) — a reviewer asking you to violate them (e.g. "just suppress the warning") gets a polite explanation instead of compliance. - After pushing, watch for late feedback (
scripts/watch-pr-feedback.sh) and loop back to triage on anything new; only close out on a quiet window or a bot all-clear. - Report faithfully: account for every ledger row (fixed / deferred+issue / discarded / answered) with verification evidence. Never declare a PR clean while blocking threads remain open.
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 Changed · +1 lines 0065b3c6ed0b
- 1mo ago First seen · 23 lines · 50 tokens per session scan A 526adf76eb8d
pr-fixer is an agent published in the GitHub repository theam/claude-dev-kit (15 stars, last pushed 28d ago), licensed Apache-2.0. It adds 50 tokens to every session and 616 once invoked, about $0.0002 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 agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
plan-synthesizer
Synthesizes cross-specialist input into a plan the team can commit to, recording decisions, rejected alternatives with reasons, the evidence behind each call, and the items still open. Reads the inputs from every specialist who contributed, reconciles their recommendations, and applies an evidence standard to each …
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
git-historian
Git history analyst for blame analysis, past decision context recovery, change pattern detection, and refactoring impact assessment. Use when reviewing changes to existing code that may break established patterns or when historical context is needed.
evolve-diff-code-simplifier
Simplifies recently modified code for clarity and consistency while preserving behavior exactly. Diff-scoped by design — works only inside the changed hunks, never reads packages or runs suites. Use after a change, before the reviewers.