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.
git clone --depth 1 https://github.com/oxy-hq/oxygenWrote 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/commands/oxy-hq/oxygen/apidoc)<a href="https://agentmods.dev/commands/oxy-hq/oxygen/apidoc"><img src="https://agentmods.dev/badge/commands/oxy-hq/oxygen/apidoc/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/commands/oxy-hq/oxygen/apidoc"><img src="https://agentmods.dev/badge/commands/oxy-hq/oxygen/apidoc.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.00000 | $0.01091 |
| Opus 5.5 | $0.00000 | $0.00436 |
| Sonnet 5.5 | $0.00000 | $0.00218 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
apidoc 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Print the bearer token (useful for raw curl calls) How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
The Oxy HTTP API lets you query databases, manage threads, trigger
workflows, and configure workspaces programmatically. All endpoints live
under /api/ and are documented in the sections below.
Authentication
Two schemes are accepted on every endpoint — supply one:
| Scheme | How to obtain | Header sent |
|---|---|---|
| API Key | Generate in Settings → API Keys | X-API-Key: <key> |
| Bearer (JWT) | Issued by oxyc login or the magic-link flow |
Authorization: Bearer <token> |
Use the Authorize button above to enter either credential; Swagger UI will attach it to every "Try it out" request.
CLI Quick-start
The terminal client is oxyc (@oxy-hq/cli, source in sdk/cli). It
replaced the old oxy api, oxy login and oxy logout subcommands, which
were removed from the oxy binary.
npm install -g @oxy-hq/cli
oxyc login — authenticate the CLI
oxyc login [--env <env>] [--target <url>] [--login-env <env>...]
Opens your browser to the Oxy web app, captures the session JWT via a
loopback callback, and caches it in the credentials file, keyed by host so
dev / prod tokens are stored separately:
~/Library/Application Support/oxy/credentials.json on macOS,
$XDG_CONFIG_HOME/oxy/credentials.json on Linux (default ~/.config). It is the same file the old
oxy login wrote, so an existing login keeps working.
oxyc login # authenticate against production
oxyc login --env local # authenticate against a local oxy serve
oxyc login --env dev --login-env staging # several deployments, one browser flow each
oxyc login --target https://my.oxy.example.com
After login, every oxyc api call for that target is automatically
authenticated — no manual token management needed.
oxyc logout # clear the cached token for the default env
oxyc logout --env local
oxyc — call the HTTP API from the terminal
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 · 118 lines · 0 tokens per session scan A 00d78b1372ac
apidoc is a command published in the GitHub repository oxy-hq/oxygen (203 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,091 tokens. 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-10-14.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
api-contract-review
Review an API contract (shapes, errors, auth model) BEFORE implementation for naming, versioning, pagination, idempotency, and fit with existing endpoints. Use when designing or changing endpoints. Do not use when the API is already implemented (use review-hard or repo-consistency-sweep).
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…