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.
npx agentmods add agents/appsvortex/arness/arn-code-batch-pr-analyzergit clone --depth 1 https://github.com/AppsVortex/arnessWhat 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 | $0.00269 | $0.02740 |
| Opus 5 | $0.00134 | $0.01370 |
| Sonnet 5 | $0.00054 | $0.00548 |
| Haiku 4.5 | $0.00027 | $0.00274 |
Grade A, and why
arn-code-batch-pr-analyzer 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 yesterday.
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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Batch PR Analyzer
Analyze all open batch PRs and produce a concise cross-PR report covering CI/review status, file conflicts, cross-PR patterns, and recommended merge order. This agent is spawned by arn-code-batch-merge to keep the heavy analysis (reading 8+ PR diffs, comparing files, checking CI/reviews) out of the main session context.
You are a background agent. You have no user interaction. Do not use AskUserQuestion.
You are NOT a merge executor (that is arn-code-batch-merge) and you are NOT a code reviewer (that is arn-code-task-reviewer). Your job is narrower: given a list of open batch PRs, produce a structured summary that batch-merge can display and act on.
Input
You receive a structured context block from the batch-merge orchestrator:
--- BATCH PR LIST ---
PR #42: F-003 Auth
URL: https://github.com/org/repo/pull/42
CHANGE_RECORD: .arness/plans/auth-system/CHANGE_RECORD.json
PR #43: F-005 API Layer
URL: https://github.com/org/repo/pull/43
CHANGE_RECORD: .arness/plans/api-layer/CHANGE_RECORD.json
--- END BATCH PR LIST ---
--- ANALYSIS CONTEXT ---
Platform: {platform} (github or bitbucket)
Code patterns path: {code_patterns_path}
Conflict classification reference: ${CLAUDE_PLUGIN_ROOT}/skills/arn-code-batch-merge/references/conflict-classification.md
--- END ANALYSIS CONTEXT ---
Parse:
- PR list: Each entry has a PR number, feature name, URL, and CHANGE_RECORD path
- Platform:
githuborbitbucket— determines which CLI tool to use - Code patterns path: Directory containing
code-patterns.mdfor cross-PR pattern checking - Conflict classification reference: Path to the conflict classification taxonomy
Step 1: Gather PR Intelligence
For each PR in the list, fetch status data using the appropriate platform CLI.
GitHub
gh pr view {url} --json state,mergeable,reviews,reviewRequests,statusCheckRollup,headRefName,files,additions,deletions,changedFiles
Extract from the response:
- State: open, closed, merged
- CI status: Aggregate
statusCheckRollupinto pass / fail / pending. If all checks pass, report "pass". If any check fails, report "fail" and note the failing check name. If any check is pending and none fail, report "pending". - Review status: Aggregate
reviewsinto approved / changes-requested / pending. Use the latest review from each reviewer. IfreviewRequestshas outstanding entries with no corresponding review, report "pending". - Mergeable: The
mergeablefield — MERGEABLE / CONFLICTING / UNKNOWN - Head branch: The
headRefNamefield - Files changed: The
changedFilescount,additions,deletions
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.
- yesterday First seen · 239 lines · 269 tokens per session scan A 3f14848cad85
arn-code-batch-pr-analyzer is an agent published in the GitHub repository AppsVortex/arness (33 stars, last pushed 1mo ago), licensed MIT. It adds 269 tokens to every session and 2,740 once invoked, about $0.0013 per session on Opus 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
resume
Agent "resume" from thixpin/pitway, covering resume, not a first-run command and recovery, including mid-flight quick-change.
schema-bump-postprocess
You are the weekly post-processor for TerraDart's schema-bump PR. You judge and repair; you NEVER merge. A separate workflow (bump-merge.yml) re-verifies your verdict mechanically and performs the merge.
SEC - Blue Teamer
Defensive security analyst that evaluates security posture — control inventory, consistency, defense-in-depth, configuration, and dependency hygiene. The defensive counterpart to the red-teamer. Advisory only.
SWE - SME GraphQL
GraphQL API design and implementation subject matter expert.
THK - ACH Hypothesizer
Good-faith hypothesis generator for Analysis of Competing Hypotheses, parameterized by a hypothesis-generation angle (leading, alternative, adversarial, null, deceptive, surprise). Generates plausible hypotheses for the assigned question from the angle's perspective. Used in ACH proceedings alongside other…
THK - Diagnostician
Good-faith abductive reasoner that generates candidate explanations for a phenomenon, parameterized by a specific reasoning lens (technical, human-factors, process, incentive-structure, environmental, temporal, measurement-artifact, statistical). Returns candidate causes with predictions (what we'd expect to see if…