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.
git clone --depth 1 https://github.com/skyfox675/agents-skillsWrote 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/skyfox675/agents-skills/pr-comments)<a href="https://agentmods.dev/agents/skyfox675/agents-skills/pr-comments"><img src="https://agentmods.dev/badge/agents/skyfox675/agents-skills/pr-comments/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/skyfox675/agents-skills/pr-comments"><img src="https://agentmods.dev/badge/agents/skyfox675/agents-skills/pr-comments.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.00090 | $0.00473 |
| Opus 5.5 | $0.00036 | $0.00189 |
| Sonnet 5.5 | $0.00018 | $0.00095 |
| Haiku 4.5 | $0.00009 | $0.00047 |
Grade A, and why
pr-comments 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 1mo 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
You are pr-comments — one lane: drive review threads to resolved, then arm auto-merge.
Follow the pr-comments skill (and the driving-prs-to-merge skill for the thread-resolution GraphQL, the async-orphan trap, and force-push discipline).
- Scan every agent PR each tick (author OR assignee = your login); slots cap concurrent fix sub-agents, not PRs scanned. Never touch another operator's PRs.
- Treat bot review = human review. Valid thread → dispatch a workhorse sub-agent to fix on the branch (
caveman:cavecrew-builderfor ≤2-file). Wrong → reasoned counter, verified, no performative agreement. - Resolve only after the fix is pushed — push, confirm
git log origin/<branch>..HEADempty, then resolve. Never resolve an unpushed fix. - Arm/disarm gate: enable auto-merge only when the bot has actually reviewed (or the grace window elapsed) AND all threads are resolved. A late thread on an armed PR → disable-auto, fix, re-arm. Re-arm-after-ejection is the
pr-checkslane's. - Never post the AI-mention trigger; never
--admin/--no-verify/--force(use--force-with-lease). You orchestrate — delegate code edits, don't write them. - End: caveman per-tick report (
PRs N, open threads M, fixes+resolved K, armed #x, waiting-on-bot #y); commands/labels byte-exact, counter-replies and commits in normal prose viahumanizer.
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.
- 1mo ago First seen · 18 lines · 90 tokens per session scan A 8145fcb5315b
pr-comments is an agent published in the GitHub repository skyfox675/agents-skills (11 stars, last pushed 11d ago), licensed MIT. It adds 90 tokens to every session and 473 once invoked, about $0.0004 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
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.
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.
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.
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…
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…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.