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/machbuilds/atom/atom-newnpx skills add machbuilds/atom --skill atom-newgit clone --depth 1 https://github.com/machbuilds/atomWhat 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.00093 | $0.00953 |
| Opus 5 | $0.00046 | $0.00477 |
| Sonnet 5 | $0.00019 | $0.00191 |
| Haiku 4.5 | $0.00009 | $0.00095 |
Grade C, and why
atom-new scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
> curl -fsSL https://raw.githubusercontent.com/machbuilds/atom/main/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> curl -fsSL https://raw.githubusercontent.com/machbuilds/atom/main/install.sh | bash How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
atom-new — bootstrap a new project from atom
This skill is a thin launcher. It does not contain the bootstrap
steps. The single source of truth is Mode 1 of AGENTS.md in the
installed atom checkout. Your job is to find that file, read it, and
run its flow conversationally against the user's chosen directory.
Why thin: atom is distributed as a git checkout that the user upgrades
in place (atom upgrade). If this skill restated the bootstrap steps,
the two would drift. Instead it points at the live instructions so the
flow is always whatever the installed atom says it is.
Step 1 — locate the installed atom
Resolve the atom source directory, in this order:
$ATOM_SOURCE_DIR(if set)$ATOM_INSTALL(if set)~/.atom/atom/(the canonical install location)
A directory is a valid atom checkout if it contains both a
VERSION file and AGENTS.md. Verify before proceeding.
If no atom checkout is found, stop and tell the user — do not improvise a bootstrap from memory:
I couldn't find an atom install (looked in
$ATOM_SOURCE_DIR,$ATOM_INSTALL, and~/.atom/atom/). Install it once with:curl -fsSL https://raw.githubusercontent.com/machbuilds/atom/main/install.sh | bashThen re-run
/atom-new.
Step 2 — read the real instructions
Read these from the resolved atom directory (not from this skill, not from memory — they evolve between releases):
AGENTS.md→ Mode 1: Bootstrap a new project. This is the canonical, ordered flow. Follow it exactly.- The docs
AGENTS.mdtells you to read, in the order it lists them (docs/VOICE.md,docs/WORKFLOW.md,docs/PATTERNS.md,docs/LESSONS_LEARNED.md,docs/HOW_TO_WRITE_CONSTITUTION.md, and the conditional ones).
Whatever Mode 1 says wins over anything summarized here.
Step 3 — ask where the project goes
This skill can fire from any directory, so you cannot assume the current working directory is where the new project should live. Before scaffolding, confirm the target:
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 · 90 lines · 93 tokens per session scan C e9988678b892
atom-new is a skill published in the GitHub repository machbuilds/atom (2 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session and 953 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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.
golden-rss
Use when testing the rss golden build.
omh-buzz
This is a Hermes-native buzz workflow skill.
redteam-api-detail-pack
Domain routing and boundary guidance for authorized API security testing, including BOLA/IDOR, authentication bypass, mass assignment, missing rate limits, and GraphQL issues. Use when a task belongs to the API testing domain and needs scope, evidence, pivot, or exit criteria.
redteam-postex-detail-pack
Domain routing and boundary guidance for authorized post-exploitation testing after initial access, including privilege escalation, persistence, lateral movement, data collection, and cleanup considerations. Use when a task belongs to the post-exploitation domain and needs scope, evidence, pivot, or exit criteria.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.