agentmods.dev

ably-cli: Skill for Claude Code

.claude/skills/ably-review/SKILL.md

ably-review is a skill for Claude Code from ably/ably-cli. It costs 101 tokens per session (3,688 once invoked), scanned A, original, Apache-2.0.

A focused code-review helper that checks only the changes on the current branch against Ably’s command-development conventions.

In plain words
What is it for?
Use it to review branch changes, check a pull request, or validate work in progress for structural and text-based issues.
Why use it?
It gives a faster, more targeted review before a pull request, without scanning the entire codebase.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions Claude Code.

This is ably/ably-cli's own configuration. It tells Claude Code how to work on ably-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ably-cli configures →

not rated 5repo 2d ago A scan 101 tokens original Apache-2.0
View source ↗ ably/ably-cli cli-web-cli.vercel.app
Reuse

Borrowing it

Nothing to install: this file belongs to ably/ably-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ably/ably-cli/main/.claude/skills/ably-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ably/ably-cli

Made for: Claude Code.

Wrote 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.

agentmods badge for ably-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/ably/ably-cli/ably-review/github.svg)](https://agentmods.dev/skills/ably/ably-cli/ably-review)
Your own site
<a href="https://agentmods.dev/skills/ably/ably-cli/ably-review"><img src="https://agentmods.dev/badge/skills/ably/ably-cli/ably-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.

agentmods 80×15 button for ably-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/ably/ably-cli/ably-review"><img src="https://agentmods.dev/badge/skills/ably/ably-cli/ably-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,688 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00101 $0.03688
Opus 5.5 $0.00040 $0.01475
Sonnet 5.5 $0.00020 $0.00738
Haiku 4.5 $0.00010 $0.00369

Measured 2mo ago against content hash b8053cf98411, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ably-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 2mo 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.

.claude/skills/ably-review/SKILL.md · 195 lines

How it starts

The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ably Branch Review

This skill reviews only the changes on the current branch (compared to main) against the conventions defined in the ably-new-command skill. It uses a combination of LSP for structural analysis (type hierarchies, call chains) and grep/read for text-pattern checks, choosing the right tool for each check.

Unlike ably-codebase-review which sweeps the entire codebase, this skill is scoped to what has changed on the current branch, making it fast and focused for pre-PR review.

Tool selection guide

Use LSP when you need type-system awareness:

  • goToDefinition — resolve what base class a command actually extends
  • findReferences — trace all callers of a method through inheritance
  • hover — reveal resolved types, inherited members, full type hierarchy
  • documentSymbol — list all methods/properties in a class structurally

Use grep/read when a text match is sufficient:

  • this.error() calls in command files
  • Component string casing in this.fail() and logCliEvent() calls
  • new Error(...) wrapping in this.fail() calls (unnecessary — accepts strings)
  • shouldOutputJson guards around this.log()
  • formatSuccess() calls ending with .
  • formatProgress() calls with manual ...
  • chalk.cyan() where formatResource() should be used
  • Quoted resource names instead of formatResource(name)
  • --json / --pretty-json in static examples arrays
  • Flag spreads like ...productApiFlags, ...durationFlag, ...clientIdFlag
  • waitUntilInterruptedOrTimeout usage
  • Missing test files (glob for them)
  • --duration flag in subscribe test files
  • Mock helper imports (getMockAblyRealtime, getMockAblyRest, getMockConfigManager)

Step 0: Verify LSP prerequisites

Before doing any analysis, check that the LSP tooling is available:

  1. Check for the LSP tool — verify the LSP tool is available in your tool list. If it is not, tell the user:

    The LSP plugin is not installed. Install it by running:

    claude plugin add anthropic/claude-code-lsp

    Then restart Claude Code and re-run this skill. Stop here — do not proceed without the LSP tool.

Read the full file on GitHub · 195 lines

Changes

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.

  1. 2mo ago First seen · 195 lines · 101 tokens per session scan A b8053cf98411

Subscribe to this mod's changes

ably-review is a skill published in the GitHub repository ably/ably-cli (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 101 tokens to every session and 3,688 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.

Code review
Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

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…

LilMGenius/paperthin · 70 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens