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/openagentsinc/openagents/openagents-clinpx skills add OpenAgentsInc/openagents --skill openagents-cligit clone --depth 1 https://github.com/OpenAgentsInc/openagentsWhat 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.00069 | $0.01525 |
| Opus 5 | $0.00034 | $0.00763 |
| Sonnet 5 | $0.00014 | $0.00305 |
| Haiku 4.5 | $0.00007 | $0.00153 |
Grade A, and why
openagents-cli 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The OpenAgents CLI
You are running inside openagents coder, which is one subcommand of the
openagents CLI. The openagents tool runs the rest of it. The same binary
answers, so what you see is this machine's build, not a remembered one.
Finding a command, and reading its answer
The openagents tool's own description lists every command and subcommand,
read from this binary. You do not need to go looking for them, and you do not
need --help to find out that a command exists.
Use <command> --help for a flag you do not know. This file lists no flags on
purpose: a written copy goes stale the first time one changes, and the help
output cannot.
Read the plain output. It is what a person reads and it is small. A list of three issues is 442 bytes plain and 20,000 as JSON, because the JSON carries every issue's whole body — and a session that reads twenty thousand bytes to answer one question pays for them on every turn after it, too.
Add --json only when you need one field out of one record. Prefer a narrower
command over a wider one you then read past: --label, --state, --limit
and a search term cost nothing and cut the answer to what was asked.
What works with no credential
openagents computer probe|policy|status— inspects this machine. The local machine controls all access; no account is involved.openagents coder --offline— answers from a built-in stand-in.openagents coder --autopilot --dry-run— prints the Autopilot plan; no model, no thread, no token.--helpanywhere.
Everything else reaches the API and needs a token. Without one you get:
openagents: No OpenAgents token is available for https://openagents.com.
Set OPENAGENTS_TOKEN.
Read that as "this person is not signed in", not as a broken command.
What signing in involves
A token is per API origin, stored in the OS credential store, and carries scopes. Two matter:
chat:account— open a thread and talk to a model.forge:write— push to the forge and write to issues, projects, and the forum.
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 · 143 lines · 69 tokens per session scan A 863e8d683223
openagents-cli is a skill published in the GitHub repository OpenAgentsInc/openagents (446 stars, last pushed 2d ago), licensed Apache-2.0. It adds 69 tokens to every session and 1,525 once invoked, about $0.0003 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-30.
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…