claude-context: Agent for Claude Code

.claude/agents/pr-discover.md

pr-discover is an agent for Claude Code from lbruton/claude-context. It costs 60 tokens per session (2,208 once invoked), scanned A, original, MIT.

A pull-request discovery and pre-analysis helper that collects review conversations, automated findings, and possible code problems into a structured report. Codacy is an automated code-quality checking service.

In plain words
What is it for?
Use it to inspect a pull-request diff, find unresolved review threads, examine automated findings, and report bugs, security issues, silent failures, or code-quality concerns.
Why use it?
It separates heavy data gathering and raw review information from the main conversation, making later review triage easier.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents.

This is lbruton/claude-context's own configuration. It tells Claude Code how to work on claude-context itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-context configures →

Reuse

Borrowing it

Nothing to install: this file belongs to lbruton/claude-context. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/lbruton/claude-context/master/.claude/agents/pr-discover.md
Clone the repo
git clone --depth 1 https://github.com/lbruton/claude-context

Made for: Claude Code.

Wrote 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.

agentmods badge for pr-discover

README.md
[![agentmods](https://agentmods.dev/badge/agents/lbruton/claude-context/pr-discover/github.svg)](https://agentmods.dev/agents/lbruton/claude-context/pr-discover)
Your own site
<a href="https://agentmods.dev/agents/lbruton/claude-context/pr-discover"><img src="https://agentmods.dev/badge/agents/lbruton/claude-context/pr-discover/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.

agentmods 80×15 button for pr-discover

Your own site · 80×15
<a href="https://agentmods.dev/agents/lbruton/claude-context/pr-discover"><img src="https://agentmods.dev/badge/agents/lbruton/claude-context/pr-discover.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,208 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00060 $0.02208
Opus 5.5 $0.00024 $0.00883
Sonnet 5.5 $0.00012 $0.00442
Haiku 4.5 $0.00006 $0.00221

Measured 5d ago against content hash 89e3842f393b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pr-discover 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 5d 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.

.claude/agents/pr-discover.md · 256 lines

How it starts

The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PR Discovery & Pre-Analysis Agent

You gather all data needed to triage a PR's review threads and quality gate findings. You run in isolation to keep the raw API responses, diffs, and Codacy reports out of main context.

Inputs

You will receive:

  • prNumber: the PR number
  • owner: GitHub owner (e.g., "lbruton")
  • repo: GitHub repo name (e.g., "StakTrakr")
  • baseBranch: the PR's base branch (e.g., "dev")
  • workingDir: absolute path to the project root

Phase 0: Pre-Analysis

Get the PR diff

cd <workingDir>
git diff origin/<baseBranch>...HEAD

Analyze the diff for issues

Read through the diff carefully and identify:

  1. Bugs and logic errors — unchecked return values, off-by-one, race conditions
  2. Silent failures — swallowed catches, inappropriate fallbacks, errors logged but not propagated
  3. Security issues — innerHTML without sanitization, raw localStorage on user content, XSS vectors
  4. Code quality — complexity, duplication introduced in this PR

Record each finding with file path, line number, severity, and description.

Phase 1: Discover Review Threads

Fetch all unresolved review threads

gh api graphql -f query='
{
  repository(owner: "<owner>", name: "<repo>") {
    pullRequest(number: <prNumber>) {
      reviewThreads(first: 50) {
        nodes {
          id
          isResolved
          comments(first: 10) {
            nodes {
              databaseId
              author { login }
              body
              path
              line
              originalLine
              createdAt
            }
          }
        }
      }
    }
  }
}'

Filter to unresolved threads only.

Check Codacy status

gh pr checks <prNumber> --json name,state,description --jq '.[] | select(.name | test("codacy|Codacy"; "i"))'

If Codacy failed or reported issues:

gh api repos/<owner>/<repo>/pulls/<prNumber>/comments --jq '.[] | select(.user.login | test("codacy"; "i")) | "\(.id) | \(.path):\(.line) | \(.body)"'

Read the full file on GitHub · 256 lines

Changes

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.

  1. 5d ago Changed 89e3842f393b
  2. 9d ago Changed 3941bbafbcef
  3. 11d ago First seen · 256 lines · 60 tokens per session scan A e15ff94bb146

Subscribe to this mod's changes

pr-discover is an agent published in the GitHub repository lbruton/claude-context (2 stars, last pushed 5d ago), licensed MIT. It adds 60 tokens to every session and 2,208 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-10-17.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens