Etymon — AI skill for Claude Code

etymon

Your team's coding tools should share the same setup.

Skills, MCP servers, agents, and rules tend to end up scattered across tool-specific folders. Someone adds a useful skill in Claude. Someone else copies it to Codex. Rules drift, server settings get missed, and the next contributor starts from scratch.

Etymon keeps that setup in your repo. Add what you need once, commit it, and let each person sync it to the tools they use.

Install

npm install -g etymon
etymon

`etymon` opens a terminal UI for adding resources, importing an existing setup, and reviewing changes before sync.

You can also run it without a global install:

npx etymon

Requires Node.js 22 or later. Git is needed for repository sources.

Start a new repo

etymon init

# Add a skill from skills.sh
etymon skills add vercel-labs/skills --skill find-skills

# Add a hosted MCP server from the official registry
etymon mcp add io.github.upstash/context7 --remote 0

# Create your own agent in the terminal form
etymon agents create

# Add guidance for part of the repo
etymon rules create --name api-guidance --dest-dir packages/api \
  --body "Keep public API responses backward compatible."

# Choose the tools you use
etymon sync --harness claude,codex,opencode

`init` sets up the manifest, lockfile, and `.gitignore`. Generated tool files stay local. Created resources go straight into `.agents/etymon/`.

Commit `.agents/etymon.toml`, `.agents/etymon.lock`, and the authored files under `.agents/etymon/`. If you register an existing local source with `add`, commit that source too.

Contributors can then run:

etymon sync

The first sync asks which tools they use. Later syncs reuse that choice. External resources restore from the recorded versions.

Bring in an existing repo

Already have skills, agents, MCP settings, or instruction files?

etymon init
etymon convert claude
etymon sync --harness codex,opencode

Replace `claude` wit