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/withoneai/one-agent-plugin/ablynpx skills add withoneai/one-agent-plugin --skill ablygit clone --depth 1 https://github.com/withoneai/one-agent-pluginWhat 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.00125 | $0.02693 |
| Opus 5 | $0.00063 | $0.01347 |
| Sonnet 5 | $0.00025 | $0.00539 |
| Haiku 4.5 | $0.00013 | $0.00269 |
Grade A, and why
ably 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 2d 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.
This is a copy
77% identical to 2-chat — 238 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ably through One
Ably Pub/Sub is a global serverless real-time messaging platform that delivers sub‑60 ms latency pub/sub capabilities—including message history, presence detection, exactly‑once delivery, and guaranteed ordering—scaling to billions of messages and millions of devices with enterprise reliability.
One exposes Ably through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.
How to run an action
- Find the action in the table below, or call
search_one_platform_actionswith platformablyif it is not listed. - Call
get_one_action_knowledgewith the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters. - Call
execute_one_actionwith parameters copied from that knowledge.
Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.
Before you start
Call list_one_integrations once and confirm Ably is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.
Each connection carries an access field. If it reports {"policy": "methods", "methods": ["GET"]} the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.
Before a write
Creates, updates, deletes and sends land on a real Ably account and cannot be recalled. State the action and the specific target in one line before the first write in a task, and let the user stop you. Reads need no confirmation.
Actions
DeviceRegistrations
| Action | Method | Path | Action id |
|---|---|---|---|
| Get a Registered Device’s Details | GET | /push/deviceRegistrations/{{deviceId}} |
conn_mod_def::GJzyoJIlY38::vCnwFRiGTgCkdMtsQsGqOQ |
| List Registered Devices | GET | /push/deviceRegistrations |
conn_mod_def::GJzyoidt0fo::o63FPpZsRCOOpxoQWOelKw |
| Register a Device for Receiving Push Notifications | POST | /push/deviceRegistrations |
conn_mod_def::GJzyoxAWBBA::xctXWeqZTDOuzu4s9ryrsA |
| Reset a Registered Device Registration’s Update Token | POST | /push/deviceRegistrations/{{deviceId}}/resetUpdateToken |
conn_mod_def::GJzyo5vgFjM::QUbrvjnsS4akBJBNURj-9w |
| Update a Device Registration | PATCH | /push/deviceRegistrations/{{deviceId}} |
conn_mod_def::GJzypiuAY8E::z6gcdNBZQ6-WqEOGwf5boQ |
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.
- 2d ago First seen · 161 lines · 0 tokens per session scan A b421143277c4
ably is a skill published in the GitHub repository withoneai/one-agent-plugin (1 stars, last pushed 13d ago), licensed MIT. It adds 125 tokens to every session and 2,693 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 77% identical to 2-chat, differing in 238 lines, and is treated as a copy.
Other skills, from other repositories
prepare-mcp-integration
Prepare MCP/vendor integrations through cited research, a content PR, exact-revision human approval, and one governed Paperclip connector PR per approved connection. Use for new integration research and delivery; not for ad hoc connector coding that bypasses the playbooks.
document-service
This skill should be used when the user asks to "analyze this codebase", "document this service", "generate technical docs", "I inherited this code", "help me understand this system", "create docs for this project", "what does this system look like", "onboard me to this codebase", "this codebase has no docs"…
hyperpod-cluster-debugger
Diagnose and remediate cluster-wide HyperPod (EKS or Slurm) problems — creation / deployment failures (CloudFormation, EFA health check, lifecycle scripts, capacity), EKS access, node replacement, CloudFormation nested-stack errors, post-maintenance rollback state, dangling nodes, autoscaler conflicts. Includes…
hyperpod-nccl
Diagnose NCCL failures and adjacent training-pod failures on HyperPod GPU clusters (EKS or Slurm) — training hangs, AllReduce / collective-op timeouts, EFA or libfabric errors, rendezvous failures, EFA TCP fallback, /dev/shm or memlock issues, NCCL version mismatch across pods, container OOM / exit-137 / OOMKilled…
planning
Discovers user intent and generates a structured, step-by-step plan for model customization workflows. This skill must always be activated alongside any other skill when the user's request relates to model customization — including fine-tuning, training, building, customizing, reviewing data, or getting advice on…
hyperpod-issue-report
Generate comprehensive issue reports from HyperPod clusters (EKS and Slurm) by collecting diagnostic logs and configurations for troubleshooting and AWS Support cases. Use when users need to collect diagnostics from HyperPod cluster nodes, generate issue reports for AWS Support, investigate node failures or…