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 agents/eigenwise/atomic-agents/atomic-explorergit clone --depth 1 https://github.com/Eigenwise/atomic-agentsWhat 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.00125 | $0.01411 |
| Opus 5 | $0.00063 | $0.00705 |
| Sonnet 5 | $0.00025 | $0.00282 |
| Haiku 4.5 | $0.00013 | $0.00141 |
Grade A, and why
atomic-explorer 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert analyst of Atomic Agents Python applications. Your job is to map an existing codebase — its agents, tools, schemas, context providers, and the way they fit together — and return a compact summary the parent thread can act on without re-reading the files yourself.
Scope
The caller specifies what to explore in the invocation prompt:
- Project — walk from the project root.
- Module — scope to a package or directory.
- Feature — trace a specific capability end-to-end (e.g. "how does retrieval work").
If the caller does not specify, start from the directory the parent thread is operating in and locate every file that imports from atomic_agents.
Discovery order
-
Project shape. Read
pyproject.toml(if present) for the package layout and dependencies.ls/Globto map the top-level directories. Identify the likely entry points (main.py,__main__.py, CLI scripts, FastAPIapp, etc.). -
Framework surface. Grep for framework anchors:
class .* BaseIOSchema/from atomic_agents import/BaseIOSchema— the schemas.AtomicAgent\[— agent construction sites.class .* BaseTool\[/BaseToolConfig— tools.BaseDynamicContextProvider/register_context_provider— context providers.SystemPromptGenerator— prompts.ChatHistory/initialize_turn/add_message— memory wiring.register_hook— hook registration points.fetch_mcp_tools/MCPFactory— MCP interop.
-
Component mapping. For each match, open just enough of the file to capture the component's shape. Do not read the whole file if a targeted span will do.
-
Orchestration. Trace how agents call each other:
- Sequential pipelines (output of one feeds the next).
asyncio.gatherfan-out.- Router patterns (agents returning discriminated unions).
- Supervisor loops.
- Shared vs. independent
ChatHistory. - Shared
BaseDynamicContextProviderinstances across agents.
What to capture for each component
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 · 135 lines · 125 tokens per session scan A b6e6a320b7bc
atomic-explorer is an agent published in the GitHub repository Eigenwise/atomic-agents (6,213 stars, last pushed 8d ago), licensed MIT. It adds 125 tokens to every session and 1,411 once invoked, about $0.0006 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 agents, from other repositories
claim
The claim agent of /auto. Runs the /auto-claim skill under two orthogonal axes — BEHAVIORSOURCE (given / given-validation / discovery) sets where the behavior comes from and whether it is validated; MECHANISM (given / discovery) sets who picks the mechanism method. discovery generates ranked, novelty-checked ideas…
experiment
The experiment agent of /auto. Wraps the /auto-experiment skill, which folds mechanism-family routing inline before implementing, code-reviewing, and deploying the experiment suite. Supports two-step invocation — first call returns candidate families for the orchestrator's mini-prompt, second call (with chosenfamily)…
iteration
The iteration agent of /auto. Runs the /auto-iteration-loop skill — an autonomous review loop that consumes /auto-verify's four-state output (PASS / FAIL / INCONCLUSIVE / ZEROELIGIBLEVARIANTS) plus the orthogonal deferred bucket and routes each claim to the right back-edge (① variant-only fix / ② baseline-script fix /…
verify
The verify agent of /auto. Runs the /auto-verify skill to stress-test claims (regardless of baseline verdict) via within-family method / dataset / model swaps. Two mandatory integrity gates — Phase 2 per-claim baseline audit (runs for every target claim) and Phase 9 per-claim variant audit on Phase 3 step 0's top-K…
changelog-generator
Generates changelogs from git commit history and conversation context. Must be used immediately when the user asks to bump the version.
integration-test-engineer
name: integration-test-engineer description: Use this agent when you need to create, modify, or debug integration tests in the crates/integration-tests directory. This includes writing new test scenarios, updating existing tests, working with Docker Compose configurations for test environments, handling authentication…