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 scylladb/scylla-cluster-tests --skill code-reviewgit clone --depth 1 https://github.com/scylladb/scylla-cluster-testsWrote 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/scylladb/scylla-cluster-tests/code-review)<a href="https://agentmods.dev/skills/scylladb/scylla-cluster-tests/code-review"><img src="https://agentmods.dev/badge/skills/scylladb/scylla-cluster-tests/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/scylladb/scylla-cluster-tests/code-review"><img src="https://agentmods.dev/badge/skills/scylladb/scylla-cluster-tests/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.00087 | $0.02665 |
| Opus 5.5 | $0.00035 | $0.01066 |
| Sonnet 5.5 | $0.00017 | $0.00533 |
| Haiku 4.5 | $0.00009 | $0.00266 |
Grade A, and why
code-review scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Trigger**: PR touches files with `curl`, `requests.get`, `requests.post`, or `remoter.run("curl`. 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 ships with it
6 files 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.
- 11d ago Changed · +6 lines · +13 tokens per session 0b0694d37f2d
- 1mo ago First seen · 209 lines · 74 tokens per session scan A 8b6796f0d4ef
code-review is a skill published in the GitHub repository scylladb/scylla-cluster-tests (72 stars, last pushed yesterday), licensed AGPL-3.0. It adds 87 tokens to every session and 2,665 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
review
Review a GitHub pull request; defaults to the current branch's PR when no number is given.
code-reviewer
A structured review process for checking whether an implementation correctly meets approved requirements and design decisions.
lld-reviewer
A review process for a low-level design (LLD), the detailed plan for implementing a system. It checks the plan against the product requirements, high-level design (HLD), API contract, and project rules.
api-reviewer
A review of an API contract, the agreed description of how software systems exchange requests, responses, events, or files.
guardrails-reviewer
A review process for project guardrails, meaning shared engineering rules that govern how work is done in a repository.
guardrails-writer
A project-wide set of engineering rules covering default practices, forbidden actions, and changes that require another review. The rules can be created from interviews or by examining an existing repository.