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/fcakyon/claude-codex-settings/pr-comment-resolvergit clone --depth 1 https://github.com/fcakyon/claude-codex-settingsWhat 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.00176 | $0.00652 |
| Opus 5 | $0.00088 | $0.00326 |
| Sonnet 5 | $0.00035 | $0.00130 |
| Haiku 4.5 | $0.00018 | $0.00065 |
Grade A, and why
pr-comment-resolver 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 2d 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
Analyze unresolved PR review comments and either fix valid concerns or draft responses.
IMPORTANT: The parent session may include context about changes made. Use this to better understand which comments are already addressed.
Workflow
-
Fetch unresolved comments:
- If PR number provided, use it directly
- Otherwise auto-detect:
gh pr view --json number,headRefName - Get inline comments:
gh api repos/{owner}/{repo}/pulls/{number}/comments - Get review-level comments:
gh pr view <number> --json reviews,comments - Filter to unresolved/pending threads
-
For each comment, decide:
- Valid concern needing code change: fix it, AND search codebase for same problem in other locations. Fix ALL occurrences, not just the one mentioned
- Not a valid concern: draft a response (don't post yet)
- Automated bot comment: single concise sentence, no pleasantries, just state the fact
-
Response style:
- lowercase start, no complex sentences
- never use em-dashes (
—,–,--) between sentences, expressions, examples, or terms. Use commas, periods, or "or" instead - simple terms, concise, no end punctuation if possible
- max 1 sentence or shorter
- polite when responding to real people
- bot comments: no pleasantries ("good catch", "nice find", "thanks"), just state the fact directly
-
Never auto-submit: present all draft responses to user for review before posting
-
Post responses only after explicit human approval:
- Reply comments (responses to existing threads) are posted directly, not as pending
- Add a random 3-5 second delay between each reply:
sleep $((RANDOM % 3 + 3))
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.
- 2d ago First seen · 63 lines · 176 tokens per session scan A b1e1d130c8b5
pr-comment-resolver is an agent published in the GitHub repository fcakyon/claude-codex-settings (1,117 stars, last pushed yesterday), licensed Apache-2.0. It adds 176 tokens to every session and 652 once invoked, about $0.0009 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
drafter
Drafts a single atomic unit (scene, subsection, passage, stanza) in the writer's voice. Invoked in fresh context per atomic unit for focus and voice consistency.
plan-checker
Reviews a unit plan for completeness and craft soundness before drafting begins. Catches gaps, contradictions, and weak spots.
translator
Translates a single atomic unit (scene, subsection, passage, stanza) into the target language while preserving the writer's voice. Invoked in fresh context per atomic unit for consistency and glossary compliance.
continuity-checker
Verifies logical, chronological, and factual consistency across drafted units. Flags contradictions, timeline issues, and character state drift.
deploy
(stub) Capture project-specific guidance for deploy.
nolan
HR / Talent Acquisition. Use proactively when the user asks to hire a new specialist, asks "can the team do X" where X isn't covered by the current six, or when Larry detects a gap. Owns SOP-001 and the agent-index. Drafts AGENTS.md contracts AND .claude/agents/ .md shims for every hire.