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 w4ngyu/openclaw-superpowers --skill receiving-code-reviewgit clone --depth 1 https://github.com/w4ngyu/openclaw-superpowersWrote 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/w4ngyu/openclaw-superpowers/receiving-code-review)<a href="https://agentmods.dev/skills/w4ngyu/openclaw-superpowers/receiving-code-review"><img src="https://agentmods.dev/badge/skills/w4ngyu/openclaw-superpowers/receiving-code-review/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/w4ngyu/openclaw-superpowers/receiving-code-review"><img src="https://agentmods.dev/badge/skills/w4ngyu/openclaw-superpowers/receiving-code-review.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.00038 | $0.01489 |
| Opus 5.5 | $0.00015 | $0.00596 |
| Sonnet 5.5 | $0.00008 | $0.00298 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
receiving-code-review 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 214 lines · 38 tokens per session scan A c9382e92b8f3
receiving-code-review is a skill published in the GitHub repository w4ngyu/openclaw-superpowers (4 stars, last pushed 5mo ago), with no licence file. It adds 38 tokens to every session and 1,489 once invoked, about $0.0002 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 skills, from other repositories
check
Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.
pr
A writing guide for creating pull request descriptions, which explain a proposed code change to reviewers. It uses sections for the summary, evidence, merge risk, and the likely area affected by the change.
code-review
A code-review skill that compares changes from a chosen commit, branch, tag, or merge-base against the repository’s coding standards and the related issue or specification.
improve-codebase-architecture
A skill that scans a codebase for places where restructuring could make future changes and testing easier, then produces an HTML report for selected improvements.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…