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 instructions/ably/ably-cli/agents-mdgit 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.07019 | $0.07019 |
| Opus 5 | $0.03510 | $0.03510 |
| Sonnet 5 | $0.01404 | $0.01404 |
| Haiku 4.5 | $0.00702 | $0.00702 |
Grade A, and why
ably-cli AGENTS.md 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Ably CLI
Mandatory Workflow
Run these IN ORDER for EVERY change:
pnpm prepare # 1. Build + update manifest
pnpm generate-doc # 2. Regenerate docs (gitignored)
pnpm exec eslint . # 3. Lint (MUST be 0 errors)
pnpm test:unit # 4. Test (at minimum)
pnpm test:tty # 5. TTY tests (local only, skip in CI)
# 6. Update docs if needed
If you skip these steps, the work is NOT complete.
Project Context
This is the Ably CLI npm package (@ably/cli), built with the oclif framework.
.
├── src/
│ ├── commands/ # CLI commands (oclif)
│ ├── services/ # Business logic
│ ├── utils/ # Utilities
│ └── base-command.ts
├── test/
│ ├── unit/ # Fast, mocked
│ ├── integration/ # Multi-component, mocked external services
│ ├── e2e/ # Full scenarios against real Ably
│ └── helpers/ # runCommand(), MockConfigManager, etc.
├── docs/ # Project docs (Testing.md, Project-Structure.md, etc.)
└── package.json # Scripts defined here
Common Pitfalls - DO NOT DO THESE
- Skip tests - Only skip with documented valid reason
- Use
_prefix for unused variables - Remove the code instead - Leave debug code - Remove ALL console.log, DEBUG_TEST, test-*.mjs
- Use
// eslint-disable- Fix the root cause - Remove tests without asking - Always get permission first
- NODE_ENV - To check if the CLI is in test mode, use the
isTestMode()helper function. process.exit- When creating a command, usethis.exit()for consistent test mode handling.console.log/console.error- In commands, always usethis.log()(stdout) for data/results and the logging helpers (this.logProgress(),this.logSuccessMessage(),this.logListening(),this.logHolding(),this.logWarning()) for status messages.console.*bypasses oclif and can't be captured by tests.- Use
Args.string()for primary entity identifiers - If the value is "what is being acted on" (name, ID, channel), represent it as a positionalArgs.string(), not aFlags.string(). Primary entity identifiers should always use camelCase.
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 · 371 lines · 7,019 tokens per session scan A 3fd616aad3db
ably-cli AGENTS.md is an instructions file published in the GitHub repository ably/ably-cli (5 stars, last pushed 15d ago), licensed Apache-2.0. It adds 7,019 tokens to every session, about $0.0351 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.