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 plugins/eigenwise/atomic-agents/marketplace/plugin marketplace add Eigenwise/atomic-agentsgit clone --depth 1 https://github.com/Eigenwise/atomic-agentsGrade A, and why
eigenwise 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 yesterday.
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.
What it actually says
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "eigenwise",
"description": "Official plugins for the Atomic Agents framework - a lightweight, modular system for building AI agents with Pydantic and Instructor",
"owner": {
"name": "Kenny Vaneetvelde",
"email": "[email protected]"
},
"plugins": [
{
"name": "atomic-agents",
"description": "Skills plus explorer and reviewer subagents for building, scaffolding, debugging, understanding, and auditing applications with the Atomic Agents Python framework. Progressive-disclosure references for schemas, agents, tools, context providers, prompts, orchestration, memory, hooks, providers, project structure, and testing — plus a troubleshoot diagnostic, isolated-context subagents for codebase mapping and code review, and a new-app scaffolder.",
"version": "2.2.0",
"author": {
"name": "Kenny Vaneetvelde",
"email": "[email protected]"
},
"source": "./claude-plugin/atomic-agents",
"category": "development",
"homepage": "https://github.com/eigenwise/atomic-agents",
"repository": "https://github.com/eigenwise/atomic-agents",
"license": "MIT",
"keywords": [
"atomic-agents",
"ai-agents",
"llm",
"pydantic",
"instructor",
"multi-agent",
"orchestration"
]
}
]
}
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.
- yesterday First seen · 35 lines scan A 66df06645f78
eigenwise is a plugin published in the GitHub repository Eigenwise/atomic-agents (6,213 stars, last pushed 8d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
mechanist
Mechanist — AI Systems as Scientific Instruments for Understanding the Mechanisms of Intelligence.
mechanist
Plugin marketplace listing 1 plugin: mechanist.
claude-md-management
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.