Atomic Agent is a local-first AI agent that runs its control loop and state on a user's machine while using local or cloud models. It drives browsers, edits files, runs approved commands, remembers context, schedules follow-ups, and connects to external tools, with the catalogue providing skills for its use.
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 skills add AtomicBot-ai/atomic-agent --skill githubgit clone --depth 1 https://github.com/AtomicBot-ai/atomic-agentWrote 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/skills/atomicbot-ai/atomic-agent/github)<a href="https://agentmods.dev/skills/atomicbot-ai/atomic-agent/github"><img src="https://agentmods.dev/badge/skills/atomicbot-ai/atomic-agent/github/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/skills/atomicbot-ai/atomic-agent/github"><img src="https://agentmods.dev/badge/skills/atomicbot-ai/atomic-agent/github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.01682 |
| Opus 5.5 | $0.00019 | $0.00673 |
| Sonnet 5.5 | $0.00010 | $0.00336 |
| Haiku 4.5 | $0.00005 | $0.00168 |
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 1mo 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 — 155 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. A token saved in the TUI (Integrations → GitHub) is
exported to gh as GITHUB_TOKEN, so either sign-in works.
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. Either rungh auth loginin your own terminal and complete the device flow, or paste a personal access token in the agent under Integrations → GitHub (/integrations). Tell me when you are done and I will re-check."
Do NOT attempt gh auth login through os.shell.run; it will hang.
remote sync is off
A git push / fetch / pull / clone through the shell can come back as
blocked by shell guard: policy.git_remote_sync_off. That is the operator's
choice, not a fault: the repository is a closed, local-only one. Do not look
for another way to reach the remote. Reply that Remote sync is off and that it
can be turned on under Integrations → GitHub, then stop.
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.
- 1mo ago Changed · +10 lines 086f580ac43c
- 1mo ago First seen · 145 lines · 48 tokens per session scan A 854a51678591
github is a skill published in the GitHub repository AtomicBot-ai/atomic-agent (3,347 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,682 once invoked, about $0.0002 per session on Opus 5.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
release-llama-launcher
Cuts a llama-launcher release: checks the release gate with go run ./cmd/release status, drafts the notes with release-notes-llama-launcher, proposes the version and has the owner confirm it, makes the two local release commits with prepare, then — after a dry run and one explicit confirmation — runs publish, which…
release-notes-llama-launcher
Builds an evidence-backed inventory of every change since llama-launcher's last published GitHub release — three blind scouts (changelog, commits, user surfaces), a merge, verification of only the contested rows — and renders plain-language release notes from it, trace-checked both ways. Read-only: it describes and…
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.
ship
Release pipeline for already-done local work. Dispatches /ground-state pre-flight, runs the project test suite, drafts a commit message, pushes, and opens a PR with a structured verification summary. Use when local changes are ready to hand off to review — e.g. 'ship this', 'push and open a PR', 'release this work'.…