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/the-open-agent/openagent/githubnpx skills add the-open-agent/openagent --skill githubgit clone --depth 1 https://github.com/the-open-agent/openagentWhat 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.00030 | $0.02264 |
| Opus 5 | $0.00015 | $0.01132 |
| Sonnet 5 | $0.00006 | $0.00453 |
| Haiku 4.5 | $0.00003 | $0.00226 |
Grade A, and why
github 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub
Overview
Prefer gh for all GitHub operations. The default goal is to complete the full GitHub flow with the least possible user effort: detect existing authentication first, reuse it if available, and only ask the user for the smallest missing step.
Never ask the user to manually perform a long GitHub setup if the agent can check, reuse, or finish it directly.
Core Rules
- Prefer
ghover raw GitHub API calls. - Prefer existing authenticated state over asking for new credentials.
- Prefer non-interactive checks before prompting the user.
- Prefer the smallest unblock request:
- paste a one-time code
- confirm browser login
- provide a PAT
- confirm repository visibility
- Do not ask the user to manually create the repository if
ghcan do it. - Do not ask the user to manually add remotes, initialize Git, or push if the agent can do it.
- Never print, echo, log, summarize, or restate secrets.
- Never store secrets in files, commits, repo config, docs, examples, or chat summaries.
- Never switch credential strategy unless the current one actually fails.
Interactive login driving rules
When using gh auth login through a shell session, do not assume the browser login step has started after the first prompt or after sending one key.
You must continue driving the interactive flow until there is explicit evidence of one of these states:
- GitHub CLI has clearly started browser/device authentication
- GitHub CLI is explicitly waiting for the user to complete external authentication
- GitHub CLI reports that authentication succeeded
- GitHub CLI reports a real error and cannot continue
While driving the login flow:
- keep polling the session after each input
- handle intermediate prompts such as protocol selection, SSH/HTTPS choice, credential helper confirmation, browser/device flow confirmation, or similar setup questions
- use minimal inputs such as
enter, arrow keys,y,n, or short submitted text as needed - do not stop after only one successful prompt response
- do not tell the user that the browser has opened unless the command output explicitly indicates that a browser login or web flow has started
- do not tell the user that login is complete unless the command output explicitly indicates success
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 · 300 lines · 30 tokens per session scan A 197e6e2caff9
github is a skill published in the GitHub repository the-open-agent/openagent (5,592 stars, last pushed 12d ago), licensed Apache-2.0. It adds 30 tokens to every session and 2,264 once invoked, about $0.0002 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
eliza-cloud
Use when the task involves Eliza Cloud or elizaOS Cloud as a managed backend, app platform, deployment target, billing layer, or monetization surface. The catch-all skill for any user request about THEIR existing apps / containers / earnings / credits / api-keys / analytics / billing / payment requests / payouts …
build-monetized-app
Use when the task is building a new app on Eliza Cloud that earns money — chat apps, agent apps, MCP-backed tools, anything that calls the cloud's chat/messages/inference endpoints on behalf of users. Covers app registration, container deploy, markup configuration, affiliate header, app charge requests, x402 payment…
discord
Use when you need to control Discord from Otto via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, set bot presence/activity, or handle moderation actions in…
eliza-cloud-buy-domain
Use whenever a user wants to register or buy a custom domain for an Eliza Cloud app — including in the same request as building the app ("build me X and put it on Y.com"). Uses Cloudflare as registrar after explicit user confirmation, paid from the user's existing cloud credit balance. Pairs with build-monetized-app…
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes, capturing pane output, and managing terminal multiplexer windows. Enables parallel coding-agent orchestration, background process management, and REPL interaction via sockets. Use when the agent needs to launch, monitor, or coordinate…