Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add iamcxa/kc-claude-plugins/plugin install kc-pr-flowWrote 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/skills/iamcxa/kc-claude-plugins/kc-pr-daemon)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/kc-pr-daemon"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-pr-daemon/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/skills/iamcxa/kc-claude-plugins/kc-pr-daemon"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-pr-daemon.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.00071 | $0.01926 |
| Opus 5 | $0.00036 | $0.00963 |
| Sonnet 5 | $0.00014 | $0.00385 |
| Haiku 4.5 | $0.00007 | $0.00193 |
Grade C, and why
kc-pr-daemon scanned grade C with 3 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 9d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
| Slack notification not arriving | Webhook URL misconfigured | Test: `curl -s -X POST "$WEBHOOK" -H 'Content-Type: application/json' -d '{"text":"test"}'` | Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/kc-plugins-config/pr-flow/daemon.yaml Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Slack notification not arriving | Webhook URL misconfigured | Test: `curl -s -X POST "$WEBHOOK" -H 'Content-Type: application/json' -d '{"text":"test"}'` | How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
All text output follows unified language preference. See plugin CLAUDE.md for query flow.
Overview
Manage the PR Review Closed-Loop Daemon — an external shell loop that automatically reviews and fixes PRs using claude -p.
Config: ~/.claude/kc-plugins-config/pr-flow/daemon.yaml
Script: ${CLAUDE_PLUGIN_ROOT}/scripts/pr-review-daemon.sh
Usage log: ~/.claude/audit/pr-daemon-usage.jsonl
Default (no subcommand)
When invoked without a subcommand (/kc-pr-daemon, pr daemon, daemon), show overview + status + next step:
PR Review Daemon
────────────────
Commands:
/kc-pr-daemon start — start daemon (mprocs or direct)
/kc-pr-daemon stop — stop daemon
/kc-pr-daemon status — usage stats (cost, iterations, last action)
/kc-pr-daemon config — view/edit settings
{status block — run the `status` bash snippet below}
Suggested next step:
{if no usage log} → /kc-pr-daemon config — set up config first
{if last run > 24h ago} → /kc-pr-daemon start — daemon not running
{if last action was STUCK} → Check PR #{N} — daemon flagged it as stuck
{if running normally} → /kc-pr-daemon status — view detailed stats
Commands
start
Option A — via project wrapper (recommended for teams):
Projects can ship a thin wrapper at .claude/scripts/pr-review-daemon.sh that reads plugin_dir from daemon.yaml and execs the plugin script. This keeps mprocs.yaml portable:
# mprocs.yaml (checked into repo — no user-specific paths)
pr-daemon:
cmd: ["bash", ".claude/scripts/pr-review-daemon.sh"]
autostart: false
env:
POLL_INTERVAL: "300"
Each user sets their plugin path in config:
# ~/.claude/kc-plugins-config/pr-flow/daemon.yaml
plugin_dir: /path/to/kc-pr-flow
Option B — direct (personal use):
cd <project-root>
bash ${CLAUDE_PLUGIN_ROOT}/scripts/pr-review-daemon.sh
Tell the user the plugin path: Read ${CLAUDE_PLUGIN_ROOT}/scripts/pr-review-daemon.sh to get the absolute path.
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.
- 9d ago First seen · 189 lines · 71 tokens per session scan C fdd8fc38ff22
kc-pr-daemon is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 1,926 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 3 findings (sends data to an external url, reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.