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 skills add ZaxbyHub/opencode-swarm --skill pr-review-fixgit clone --depth 1 https://github.com/ZaxbyHub/opencode-swarmWrote 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/zaxbyhub/opencode-swarm/pr-review-fix)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/pr-review-fix"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/pr-review-fix/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/zaxbyhub/opencode-swarm/pr-review-fix"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/pr-review-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 10 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 21 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00052 | $0.00298 |
| Opus 5 | $0.00026 | $0.00149 |
| Sonnet 5 | $0.00010 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
pr-review-fix 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 10d 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
PR Review Fix
Compatibility adapter. Prefer $swarm-pr-feedback for all new PR feedback work.
Read ../../../.opencode/skills/swarm-pr-feedback/SKILL.md for the canonical
workflow.
Codex-specific execution notes:
- Treat each review item as a claim to verify against the current branch or live PR head before editing.
- Use the GitHub app when available, or
gh, to inspect unresolved review threads and PR metadata. - For bot or app reviews, inspect both the review comment and any commits the bot pushed; compare each claim against branch history and current code before classifying it.
- Use
rg, file reads, and tests to classify each item as confirmed, disproved, pre-existing, or unverified. - Patch only confirmed gaps unless the user explicitly asks for speculative cleanup.
- Do not resolve GitHub review threads unless the user explicitly instructs it.
- Load
.agents/skills/commit-pr/SKILL.mdbefore committing, pushing, or updating the PR.
When review feedback involves tests, also load $writing-tests; when it involves runtime invariants, also load $engineering-conventions.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 24 lines · 52 tokens per session scan A dde5671e432f
pr-review-fix is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (467 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 298 once invoked, about $0.0003 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 skills, from other repositories
armada-ledger
Pick the right ledger for a finding. Use when writing defects, adversarial findings, or security findings. Triggers on: ledger, defect, adversarial, security finding, DEF-001, ADV-001, SEC-001.
armada-pr
PR-first finish for a feature lane. Use before reporting a feature done. Triggers on: PR, finish feature, gh pr create, merge, lane complete.
generic-fullstack-code-reviewer
Review full-stack code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md compliance. Enforces TypeScript strict mode, input validation, GPU-accelerated animations, and design system consistency. Use when completing features, before commits, or reviewing pull requests.
armada-gate
Run an evidence-gate checklist for each success criterion in the current phase. Use when checking if a phase is complete before marking it passed.
atomic-review
Compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", or invokes /atomic-review. Auto-triggers when reviewing pull requests.
generic-code-reviewer
Review code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md workflow compliance. Supports any tech stack - HTML/CSS/JS, React, TypeScript, Node.js, Python, NestJS, Next.js, and more. Use when completing features, before commits, or reviewing pull requests.