Borrowing it
Nothing to install: this file belongs to megamen32/gptadmin_opensource. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/megamen32/gptadmin_opensource/main/.opencode/skills/swarm-pr-feedback/SKILL.mdgit clone --depth 1 https://github.com/megamen32/gptadmin_opensourceWrote 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/megamen32/gptadmin_opensource/swarm-pr-feedback)<a href="https://agentmods.dev/skills/megamen32/gptadmin_opensource/swarm-pr-feedback"><img src="https://agentmods.dev/badge/skills/megamen32/gptadmin_opensource/swarm-pr-feedback.svg" alt="Measured on agentmods" 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.00088 | $0.05759 |
| Opus 5 | $0.00044 | $0.02880 |
| Sonnet 5 | $0.00018 | $0.01152 |
| Haiku 4.5 | $0.00009 | $0.00576 |
Grade A, and why
swarm-pr-feedback 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 6d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 6d ago First seen · 477 lines · 88 tokens per session scan A 8b50211ed75e
swarm-pr-feedback is a skill published in the GitHub repository megamen32/gptadmin_opensource (10 stars, last pushed today), licensed AGPL-3.0. It adds 88 tokens to every session and 5,759 once invoked, about $0.0004 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-31.
Other skills, from other repositories
code-review
Review the current diff, or a PR number/branch/path target, for correctness bugs and reuse/simplification/efficiency cleanups at the given effort level (low/medium: fewer, high-confidence findings; high→max: broader coverage, may include uncertain findings; ultra: deep multi-agent review in the cloud); with no level…
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
twin-pr-triage
Scan open pull requests, assess risk and complexity, and build a prioritized review queue. Used by digital twin personas to reduce PR review cognitive load.
fulcra-agent-forge
Bridge GitHub into a fulcra-agent-teams review flow: mirror PR state onto the team store as evidence, and auto-approve a review when its PR merges — so review status reflects the forge even when no human files a verdict.
gitlab-merge-request-review
Review and merge GitLab merge requests via the gitlab-api MCP server — by default the MRs assigned to you or where you are a reviewer, optionally scoped to a project, group, or the whole instance. Read an MR, gate it on a green pipeline (pipeline → jobs → job log), then approve, accept/merge, or set…
review-changes
Review current staged, unstaged, and untracked Git changes for correctness and regression risk, grounded in changed paths, diffs, focused file reads, and nearby test discovery. Use when the user asks to review local changes or a working-tree diff; do not use for broad repository audits.