setup

setup is a skill for Claude Code from atomgit-atomcode/atomcode. It costs 71 tokens per session (3,429 once invoked), scanned C, original, MIT.

A codebase analysis tool that recommends AtomCode automations, such as hooks, subagents, skills, plugins, and MCP servers. It examines the project and suggests a small set of relevant improvements.

In plain words
What is it for?
Use it when setting up AtomCode, improving project workflows, or choosing automations for a specific codebase. It recommends changes first and offers installation separately.
Why use it?
It helps identify useful automation opportunities without requiring you to know which extension type fits a problem.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents.

Good fit Use it when setting up AtomCode, improving project workflows, or choosing automations for a specific codebase. It recommends changes first and offers installation separately.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atomgit-atomcode/atomcode/atomcode-automation-recommender
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.

Any agent
npx skills add atomgit-atomcode/atomcode --skill atomcode-automation-recommender
Clone the repo
git clone --depth 1 https://github.com/atomgit-atomcode/atomcode

Made for: Claude Code.

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.

agentmods badge for setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/atomgit-atomcode/atomcode/atomcode-automation-recommender/github.svg)](https://agentmods.dev/skills/atomgit-atomcode/atomcode/atomcode-automation-recommender)
Your own site
<a href="https://agentmods.dev/skills/atomgit-atomcode/atomcode/atomcode-automation-recommender"><img src="https://agentmods.dev/badge/skills/atomgit-atomcode/atomcode/atomcode-automation-recommender/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.

agentmods 80×15 button for setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/atomgit-atomcode/atomcode/atomcode-automation-recommender"><img src="https://agentmods.dev/badge/skills/atomgit-atomcode/atomcode/atomcode-automation-recommender.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,429 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.03429
Opus 5.5 $0.00028 $0.01372
Sonnet 5.5 $0.00014 $0.00686
Haiku 4.5 $0.00007 $0.00343

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

Security

Grade C, and why

setup 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 4d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

2. 权限不足 — 尝试 sudo 或检查目录权限

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

cat .mcp.json 2>/dev/null || echo '{}'
crates/atomcode-capabilities/assets/setup-seeds/skills/atomcode-automation-recommender/SKILL.md · 394 lines

How it starts

The opening of the file, as written. The whole thing — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AtomCode Automation Recommender

Analyze codebase patterns to recommend tailored AtomCode automations, then offer to install them.

Core Principles

  1. Recommend first, install on request — output recommendations, then ask "要我帮你装上吗?"
  2. Online search first, local fallback — try npx skills find for the latest community skills; fall back to reference files if Node.js unavailable
  3. Friendly error handling — if tools are missing (no Node.js, no npx), explain clearly and continue with local recommendations
  4. 1-2 per category — don't overwhelm; surface the most valuable automations

Automation Types

Type Best For How to Install
Skills Packaged expertise, workflows, repeatable tasks npx skills add <pkg> or create .atomcode/skills/<name>/SKILL.md
Plugins Collections of skills, commands, agents, hooks /plugin marketplace add <url> then /plugin install <name>
MCP Servers External tool integrations (databases, APIs, docs) Write to .mcp.json (project root) or ~/.atomcode/mcp.json (global)
Hooks Automatic actions on tool events (format, lint, block) Write to .atomcode/settings.json
Subagents Specialized reviewers (security, performance, a11y) Create .atomcode/skills/<name>/SKILL.md with reviewer prompt
Commands Quick slash commands (/test, /review, /deploy) Create .atomcode/commands/<name>.md

Workflow

Phase 1: Codebase Analysis

Gather project context:

# Detect project type and tools
ls -la package.json pyproject.toml Cargo.toml go.mod pom.xml build.gradle 2>/dev/null
cat package.json 2>/dev/null | head -50

# Check dependencies
cat package.json 2>/dev/null | grep -E '"(react|vue|angular|next|express|fastapi|django|prisma|supabase|stripe)"'

# Check existing AtomCode config
ls -la .atomcode/ CLAUDE.md .mcp.json 2>/dev/null

# Project structure
ls -la src/ app/ lib/ tests/ components/ pages/ api/ 2>/dev/null

Read the full file on GitHub · 394 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 4d ago Changed a167c77aad96
  2. 1mo ago First seen · 394 lines · 71 tokens per session scan C 747ec881c253

Subscribe to this mod's changes

setup is a skill published in the GitHub repository atomgit-atomcode/atomcode (206 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 3,429 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 2 findings (asks for root, reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens