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 agentmods add skills/ably/ably-cli/ably-new-commandnpx skills add ably/ably-cli --skill ably-new-commandgit clone --depth 1 https://github.com/ably/ably-cliWhat 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 | $0.00107 | $0.07523 |
| Opus 5 | $0.00053 | $0.03762 |
| Sonnet 5 | $0.00021 | $0.01505 |
| Haiku 4.5 | $0.00011 | $0.00752 |
Grade A, and why
ably-new-command 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 489 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ably CLI New Command
This skill helps you create new commands for the Ably CLI, including the command file, test file, and any needed index/topic files. The Ably CLI is built on oclif (TypeScript) and has strict conventions that every command must follow.
Step 1: Identify the command pattern
Every command in this CLI falls into one of these patterns. Pick the right one based on what the command does:
| Pattern | When to use | Base class | Client | Example |
|---|---|---|---|---|
| Subscribe | Long-running event listener | AblyBaseCommand |
Realtime | channels subscribe, rooms messages subscribe |
| Publish/Send | Send messages | AblyBaseCommand |
REST or Realtime | channels publish, rooms messages send |
| History | Query past messages/events | AblyBaseCommand |
REST | channels history, rooms messages history |
| Get | One-shot query for current state | AblyBaseCommand |
REST | channels occupancy get, rooms occupancy get |
| List | Enumerate resources via REST API | AblyBaseCommand |
REST | channels list, rooms list |
| Enter | Join presence/space then optionally listen | AblyBaseCommand |
Realtime | channels presence enter, spaces members enter |
| REST Mutation | One-shot REST mutation (no subscription) | AblyBaseCommand |
REST | rooms messages update, rooms messages delete |
| CRUD | Create/read/update/delete via Control API | ControlBaseCommand |
Control API (HTTP) | integrations create, queues delete |
Specialized base classes — some command groups have dedicated base classes that handle common setup (client lifecycle, cleanup, shared flags):
| Pattern | Base class | When to use | Source |
|---|---|---|---|
| Chat commands | ChatBaseCommand |
rooms messages, rooms reactions, rooms typing, rooms occupancy |
src/chat-base-command.ts |
| Spaces commands | SpacesBaseCommand |
spaces members, spaces locks, spaces cursors, spaces locations |
src/spaces-base-command.ts |
| Stats commands | StatsBaseCommand |
stats app, stats account |
src/stats-base-command.ts |
What ships with it
2 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.
- yesterday First seen · 489 lines · 107 tokens per session scan A 265d9f901fdc
ably-new-command is a skill published in the GitHub repository ably/ably-cli (5 stars, last pushed 15d ago), licensed Apache-2.0. It adds 107 tokens to every session and 7,523 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…