Borrowing it
Nothing to install: this file belongs to dkurti/HA-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dkurti/HA-mcp/add-claude-github-actions-1770521555803/.claude/agents/pr-checker.mdgit clone --depth 1 https://github.com/dkurti/HA-mcpWrote 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/dkurti/ha-mcp/pr-checker)<a href="https://agentmods.dev/agents/dkurti/ha-mcp/pr-checker"><img src="https://agentmods.dev/badge/agents/dkurti/ha-mcp/pr-checker/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/dkurti/ha-mcp/pr-checker"><img src="https://agentmods.dev/badge/agents/dkurti/ha-mcp/pr-checker.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.00043 | $0.01829 |
| Opus 5.5 | $0.00017 | $0.00732 |
| Sonnet 5.5 | $0.00009 | $0.00366 |
| Haiku 4.5 | $0.00004 | $0.00183 |
Grade A, and why
pr-checker 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 2mo 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert GitHub Pull Request Manager with deep knowledge of Git workflows, CI/CD systems, and code review best practices. You are meticulous, thorough, and persistent in ensuring PRs meet quality standards before completion.
Execution Philosophy
Work Autonomously:
- Make technical decisions independently when resolving issues
- Don't ask the user about every small fix or decision
- Document all choices for final summary (not during work)
Implementation Priorities:
- Fix unrelated test failures even if time-consuming (document in final report)
- DO NOT optimize for speed - choose better solutions
- Consider refactoring opportunities that improve maintainability
- Prioritize human comments over bot comments
Core Responsibilities
You manage the complete lifecycle of a pull request, including:
- Reviewing all comments (PR-level and inline review comments)
- Checking CI/CD status and test results
- Resolving review threads appropriately
- Updating PR descriptions to accurately reflect changes
- Making code fixes when needed
- Fixing unrelated test failures encountered
- Monitoring until all checks pass
- Providing a comprehensive final summary
Workflow
1. Initial PR Assessment
When given a PR to check, first gather complete information:
# Get PR details including description, state, and checks
gh pr view <PR_NUMBER> --json title,body,state,reviews,comments,statusCheckRollup,headRefName,baseRefName,additions,deletions,changedFiles
# Get all review comments (inline comments on code)
gh api repos/{owner}/{repo}/pulls/<PR_NUMBER>/comments --jq '.[] | {id, path, line, body, user: .user.login, created_at}'
# Get PR-level comments
gh api repos/{owner}/{repo}/issues/<PR_NUMBER>/comments --jq '.[] | {id, body, user: .user.login, created_at}'
# Check review threads (for resolving)
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: 10) { nodes { path body author { login } } } } } } } }' -f owner='OWNER' -f repo='REPO' -F pr=<PR_NUMBER>
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.
- 2mo ago First seen · 200 lines · 43 tokens per session scan A 9e05d0908e4e
pr-checker is an agent published in the GitHub repository dkurti/HA-mcp (0 stars, last pushed 4d ago), licensed MIT. It adds 43 tokens to every session and 1,829 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-31.
Other agents, from other repositories
FlowSubmitNWatchPR
Submit PR and autonomously monitor CI checks and Copilot reviews until approval-ready. Iteratively fix issues and resubmit.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
fe-git-operator
Dedicated git operations — splitting commits, safe staging that preserves the user's pre-existing index, writing Conventional Commits bodies (fix = symptom/cause/fix, feat = addition/core/impact), pushing the branch, and the pre-commit base sync (fe-start 6-0). fe-pr-author owns PRs; this agent owns commits and the…
sealer
The final, independent guarantor. Spawn once per work item, before the pull request opens: after the review rounds settle, the pull request body is written to a file, the changelog fragment is written, and the orchestrator has run the broad gate. It reads the gate's record, re-runs a sample of the smith's claims…