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 wttr-weathergit 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/wttr-weather)<a href="https://agentmods.dev/skills/atomicbot-ai/atomic-agent/wttr-weather"><img src="https://agentmods.dev/badge/skills/atomicbot-ai/atomic-agent/wttr-weather/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/wttr-weather"><img src="https://agentmods.dev/badge/skills/atomicbot-ai/atomic-agent/wttr-weather.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.00025 | $0.00191 |
| Opus 5.5 | $0.00010 | $0.00076 |
| Sonnet 5.5 | $0.00005 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
wttr-weather 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
No `wttr` binary. No `skill.run_script`. Fallback: `curl -fsS --max-time 25 '<url>'` via `os.shell.run`. What it actually says
wttr-weather
os.http.request GET (allowlist must include wttr.in if not null):
https://wttr.in/<Place>?format=3— one-line texthttps://wttr.in/<Place>?format=j1— JSON- No place:
https://wttr.in/?format=3 - Metric/imperial: append
&mor&u
No wttr binary. No skill.run_script. Fallback: curl -fsS --max-time 25 '<url>' via os.shell.run.
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 First seen · 21 lines · 25 tokens per session scan A 0bd3accc3ca2
wttr-weather is a skill published in the GitHub repository AtomicBot-ai/atomic-agent (3,436 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 191 once invoked, about $0.0001 per session on Opus 5.5. 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-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.
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…
manage-llm-server
Inspect and control the local LLM server(s) via llama-launcher — list profiles, see what's running, switch models, tail logs. Use when the user wants to know what model is loaded, change models, start/stop or restart the server, or troubleshoot a stuck load.
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…
browse
Use the browse CLI for Browserbase browser automation, Browserbase cloud APIs, Browserbase Functions, templates, web fetch/search, diagnostics, and Browse.sh skill discovery/installation. Use when the user asks to navigate pages, inspect browser state, run local or remote browser sessions, manage Browserbase…
opencli-usage
Discover and invoke OpenCLI capabilities for websites and Chrome. Find commands, inspect schemas, interpret results and choose browser or adapter tools.