leon4z

Modus — AI skill for Claude Code

AI community

Local-first macOS app to manage AI coding rules, Skills, MCP, and configs across Cursor, Claude Code, Codex, and more.

How to install Modus

This entry records only its repository, not the path inside it, so there is no exact command to give. Open leon4z/Modus and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Modus does

Local-first macOS app to manage AI coding rules, Skills, MCP, and configs across Cursor, Claude Code, Codex, and more.

Alternatives in AI

Skills Manage — Desktop app to manage AI coding agent skills across Claude Code, Cursor, Gemini CLI, Codex, and 20+ platforms 2.2k ★
Token Monitor — Local-first desktop widget for tracking token usage, costs, and limits across 32+ AI coding tools—including Cl 1.8k ★
Rulesync — by dyoshikawa - A Node.js CLI tool that automatically generates configs (rules, ignore files, MCP servers, com 909 ★

README

Modus

**A local-first macOS desktop app for managing AI coding tool rules, Skills, MCP, and configs.**

[简体中文](README.zh-CN.md) · [Docs](docs/README.md) · [Changelog](docs/changelog.md)

![Modus dashboard](docs/assets/dashboard_en.png)

Why Modus?

AI coding tools often keep their rules, Skills, MCP entries, and configuration files in different local paths. A rule that works well in one agent often has to be copied and edited again for another tool. Whether a Skill is actually available to a specific tool can also require checking folders and tool-specific behavior by hand.

Modus gives those local assets one visible, reusable, and auditable workspace. You can manage rules, Skills, MCP, and config files in one interface, then review the exact file changes before anything is written.

Tool support is based on each tool's official documentation plus local verification of real macOS behavior, especially when the docs do not fully specify where rules, Skills, MCP, or config sources live on disk. Modus treats support as a capability matrix, so a tool can be supported for discovery or read-only review even when a specific write action has not been verified.

Highlights

Inject one global rule set across tools: Maintain shared rules once and sync them into supported tools so different agents work under the same constraints without repeated manual edits.
See whether a Skill is usable by each tool: Skill cards show per-tool availability, making it clear which tools can currently use a given Skill.
Support shared Skills and tool-local Skills: Modus distinguishes tools that support user-level shared Skills