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/KaimingWan/oh-my-kiroWrote 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/kaimingwan/oh-my-kiro/fixpr)<a href="https://agentmods.dev/commands/kaimingwan/oh-my-kiro/fixpr"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/fixpr.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.00000 | $0.00819 |
| Opus 5 | $0.00000 | $0.00409 |
| Sonnet 5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
fixpr 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 8d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automated PR fixer: fetch all review comments, triage each one, fix or pushback, reply + resolve every thread. Zero unresolved threads when done.
Step 1: Understand the PR
gh pr view <PR> --json number,title,body,headRefName,baseRefName,files,additions,deletions
gh pr diff <PR>
Read the full diff. Understand what the PR does and why — this context guards against drift when fixing individual comments.
Step 2: Fetch ALL Unresolved Review Threads
This step is MANDATORY. Do NOT skip it.
gh api graphql -f query='
query($owner:String!,$repo:String!,$pr:Int!) {
repository(owner:$owner,name:$repo) {
pullRequest(number:$pr) {
reviewThreads(first:100) {
nodes {
id
isResolved
comments(first:5) {
nodes { id body author { login } path line }
}
}
}
}
}
}' -f owner='<OWNER>' -f repo='<REPO>' -F pr='<PR_NUMBER>'
Filter to unresolved threads. If zero unresolved → report "nothing to fix" and stop.
Step 3: Triage Every Thread
For each unresolved thread, decide:
| Verdict | Meaning | Action |
|---|---|---|
| AGREE | Reviewer is right | Fix the code |
| PUSHBACK | Current code is intentional or reviewer misunderstood | Explain why, don't change code |
Show the triage table to the user before proceeding:
| # | Thread ID | File:Line | Comment (summary) | Verdict | Reason |
Step 4: Fix Code (AGREE items only)
For each AGREE item:
- Make the minimal code change
- Verify the fix doesn't break other parts of the PR
After all AGREE fixes: run build/lint/typecheck if applicable.
Step 5: Reply + Resolve EVERY Thread
CRITICAL: Both AGREE and PUSHBACK threads get a reply AND a resolve. No exceptions.
For AGREE threads:
# Reply with what was fixed
gh api graphql -f query='mutation($tid:ID!,$body:String!) {
addPullRequestReviewThreadReply(input: {pullRequestReviewThreadId:$tid, body:$body}) {
comment { id }
}
}' -f tid='<THREAD_ID>' -f body='Fixed: <what changed>'
# Resolve
gh api graphql -f query='mutation($tid:ID!) {
resolveReviewThread(input:{threadId:$tid}) { thread { isResolved } }
}' -f tid='<THREAD_ID>'
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.
- 8d ago First seen · 113 lines · 0 tokens per session scan A e90517e05705
fixpr is a command published in the GitHub repository KaimingWan/oh-my-kiro (103 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 819 tokens. 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 commands, from other repositories
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
code-review
Code review for branch changes. Analyzes git diff between branches with multi-level depth (low/medium/high). Matches changes against task description. Returns structured report with severity levels and verdict.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.