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/atomicbot-ai/atomic-agent/githubnpx skills add AtomicBot-ai/atomic-agent --skill githubgit clone --depth 1 https://github.com/AtomicBot-ai/atomic-agentWhat 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.00048 | $0.01525 |
| Opus 5 | $0.00024 | $0.00763 |
| Sonnet 5 | $0.00010 | $0.00305 |
| Haiku 4.5 | $0.00005 | $0.00153 |
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 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
github
Use the official gh CLI as the GitHub gateway.
Prefer gh over raw REST; fall back to gh api <endpoint> only when a verb is
missing. gh already speaks the user's authenticated identity, so no tokens are
handled in this skill.
Setup check (lazy — do NOT probe every turn)
Do not run gh auth status before each request. Just run the gh
command the user asked for — reads go straight through. Only when a command
fails map the error to a Setup playbook branch:
- stderr contains
command not found: gh→ Setup playbook → "gh is not installed". - stderr contains
not logged/gh auth login→ Setup playbook → "not authenticated".
If unsure which branch applies, capture stderr and ask the user before proceeding.
Setup playbook (when prerequisites are missing)
When a check fails, OFFER concrete help and EXECUTE the fix yourself — do not dump install docs on the user.
gh is not installed
Reply (solo reply step):
"The GitHub CLI (
gh) is not installed. I can install it with Homebrew (brew install gh) — you will be asked to confirm. Install it?"
On yes:
[{ "tool": "os.shell.run", "args": { "cmd": "brew", "args": ["install", "gh"] } }]
If brew itself is missing, do NOT bootstrap Homebrew — point the user at
https://cli.github.com/ for their platform, then stop.
not authenticated
gh auth login is interactive (opens a browser / device flow) and cannot run
from a non-interactive tool shell. Reply:
"
ghis installed but not authenticated. Rungh auth loginin your own terminal and complete the device flow, then tell me when you are done and I will re-check."
Do NOT attempt gh auth login through os.shell.run; it will hang.
When to use
- Inspect or manage GitHub repos, issues, PRs, releases, gists, Actions runs.
- "Open a PR", "list my issues", "what's failing in CI", "create a release".
When NOT to use
- Local git operations (commit, branch, diff) — use the
os.git.*tools. - Non-GitHub forges (GitLab, Bitbucket) —
ghonly speaks GitHub. - Scheduling agent-driven background work — use
tasks.schedule/tasks.cron.
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 · 145 lines · 48 tokens per session scan A 854a51678591
github is a skill published in the GitHub repository AtomicBot-ai/atomic-agent (2,425 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 1,525 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
harness-init-runner
Initialize a lightweight repo-local Node.js harness (harness/ + .harness/) WITHOUT AIOS dependency. Use ONLY when you need a standalone, portable harness. If AIOS is installed, use aios-long-running-harness instead — it has rex Command hosting, ContextDB integration, and checkpoint recovery.
brand-asset-retrieval
Professional retrieval of corporate brand assets from URLs. Use this skill to automatically identify and extract high-resolution logos, favicons, and primary brand colors from a website to ensure consistency in generated deliverables.
opencli-usage
Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
pinchtab-stealth-score
Run the PinchTab stealth-score sweep against 15 bot-detection / fingerprint sites (sannysoft, rebrowser, deviceandbrowserinfo, iphey, whoer, browserscan, pixelscan, fingerprint-scan, incolumitas, fvision, amiunique, browserleaks, creepjs, coveryourtracks, fingerprint-demo). Starts a Docker PinchTab container per…