What is atomic-explorer?

A code-exploration agent that maps an existing Atomic Agents Python application. It catalogs agents, tools, schemas, context providers, and how data moves between them.

Use it to understand, document, or trace an Atomic Agents project, module, or feature from its entry point through agents, tools, schemas, and context providers.

It turns an unfamiliar codebase into a compact architecture overview, so you can locate the important pieces without reading every file first.

atomic-explorer — Agent for Claude Code by Eigenwise/atomic-agents

About the project

Atomic Agents is a lightweight, modular framework for assembling AI agents and applications from single-purpose components such as agents, tools, and context providers. It is for developers building maintainable agentic AI pipelines with reusable, composable parts and structured outputs. The catalogue entries provide agent skills, instructions, settings, and related development workflows for the framework.

Eigenwise/atomic-agents · 6,319 stars · on GitHub · eigenwise.github.io

Install

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.

Clone the repo

git clone --depth 1 https://github.com/Eigenwise/atomic-agents

Made for: Claude Code.

Or install atomic-agents, the plugin that ships this one along with the rest of its 7 skills, 2 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/eigenwise/atomic-agents/atomic-explorer/github.svg)](https://agentmods.dev/agents/eigenwise/atomic-agents/atomic-explorer)

Your own site

<a href="https://agentmods.dev/agents/eigenwise/atomic-agents/atomic-explorer"><img src="https://agentmods.dev/badge/agents/eigenwise/atomic-agents/atomic-explorer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/eigenwise/atomic-agents/atomic-explorer"><img src="https://agentmods.dev/badge/agents/eigenwise/atomic-agents/atomic-explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 125 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,411 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00125	$0.01411
Opus 5.5	$0.00050	$0.00564
Sonnet 5.5	$0.00025	$0.00282
Haiku 4.5	$0.00013	$0.00141

Measured 2mo ago against content hash b6e6a320b7bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

claude-plugin/atomic-agents/agents/atomic-explorer.md · 135 lines

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/Glob to map the top-level directories. Identify the likely entry points (main.py, __main__.py, CLI scripts, FastAPI app, 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.gather fan-out.
- Router patterns (agents returning discriminated unions).
- Supervisor loops.
- Shared vs. independent ChatHistory.
- Shared BaseDynamicContextProvider instances across agents.

What to capture for each component

Read the full file on GitHub · 135 lines

Changes

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.

2mo ago First seen · 135 lines · 125 tokens per session scan A b6e6a320b7bc

Subscribe to this mod's changes

atomic-explorer is an agent published in the GitHub repository Eigenwise/atomic-agents (6,319 stars, last pushed 8d ago), licensed MIT. It adds 125 tokens to every session and 1,411 once invoked, about $0.0005 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.

Building agents ai artificial-intelligence large-language-model large-language-models llms openai

atomic-explorer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
atomic-explorerEigenwise/atomic-agents	Agent	6.3k	8d ago	MIT	A	125	Claude Code
experimentzjunlp/Mechanist	Agent	79	1mo ago	MIT	A	72	Claude Code
iterationzjunlp/Mechanist	Agent	79	1mo ago	MIT	A	143	Claude Code
verifyzjunlp/Mechanist	Agent	79	1mo ago	MIT	B	0	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code