my-ai-tools CLI
An installer that sets up one set of rules, skills, hooks and MCP servers across Claude Code, Codex, Cursor and more.
- 129 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The script replaces agent configuration files and installs default programs, and the remote installer runs right after download.
- On Windows it installs Git, `jq` and Node.js through `winget`, and the system may ask for administrator rights.
Install
- Works in
Manual install
curl -fsSL https://ai-tools.itman.fyi/install.sh | bashOne-line install for macOS, Linux and WSL. Saving the script and starting with `--dry-run` is safer.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The script replaces agent configuration files and installs default programs, and the remote installer runs right after download.
- On Windows it installs Git, `jq` and Node.js through `winget`, and the system may ask for administrator rights.
This is third-party code. Review the repository files before installing.
What it does
`my-ai-tools` keeps AI coding assistant configuration in a repository and installs it on a machine with one command. A single set of agent guidelines, skills, commands, hooks, MCP server definitions and tool settings is laid out across Claude Code, OpenCode, Amp, Codex, Cursor, Pi, Antigravity and many others. An export brings local configuration changes back into the repository, so sync runs both ways. Before installing there is a side-effect-free `--dry-run` and a `--backup` copy. JSON and other supported configuration files are validated before writing. In `--yes` mode the default tools are installed (Amp, Pi, Codex, OpenCode, Claude Code, Grok, qmd, rtk, ctx, open-cursor, ai-switcher, open_code_review, Plannotator), along with shared skills and MCP and plugin configuration for the selected agents. The installer works on macOS, Linux, Windows 11 and WSL.
Who it is for. Developers who use several AI assistants across machines and want to keep their settings in one repository.
Good fit when
- A new machine needs the same skills, hooks and MCP servers for Claude Code, Codex and Cursor.
- You want a `--dry-run` to see the changes before writing into existing configurations.
- Local agent settings must be brought back into the repository so they are not lost between machines.
- You need to deploy the set on Windows 11 without manually installing Git Bash, `jq` and Node.js.
Not a fit when
- You need only one setting for one agent: the tool installs a whole set and can replace existing files.
- You do not want to run a remote script: the one-line installer downloads and executes it at once.
- You need control over every package: some optional tools are skipped with a warning when they fail.
Example request
Show what my-ai-tools would install by running `bash install.sh --dry-run`, and only then install with `--backup`.Limitations
The installer can replace existing configuration files, so run `--dry-run` first and add `--backup`. The one-line `curl ... | bash` command downloads and runs a remote script, and the author advises saving and reading it first. On Windows PowerShell the script installs missing programs through `winget`, and Windows may ask for administrator rights for Git or Node.js. Base requirements for macOS, Linux and WSL are Bash 3.0 or newer, Git and `curl`, plus Bun or Node.js LTS. Optional tools are skipped on failure, while Claude, Amp, Codex and required dependencies (qmd, ctx, Plannotator) stop the install with a nonzero exit code.
How to disable. The installed files live in each agent settings directory, for example `~/.claude/`, and are removed by hand. `--backup` copies let you restore previous configurations. Details of the contents are on the ai-tools.itman.fyi docs site.
FAQ
How do I install my-ai-tools safely?
Download the script with `curl -fsSL https://ai-tools.itman.fyi/install.sh -o install.sh`, read it, run `bash install.sh --dry-run`, then `bash install.sh --backup`. A dry run changes nothing.
Which assistants are supported?
Claude Code, OpenCode, Amp, Codex, Cursor, Pi, Antigravity and many others. The catalog of tools shows in `./cli.sh --help`, and extras are set with the `--with-tools` flag.
How do I install on Windows 11?
In PowerShell run `Invoke-RestMethod https://ai-tools.itman.fyi/install.ps1 | Invoke-Expression`. The script installs Git, `jq` and Node.js LTS through `winget` if missing. It is better to save and read `install.ps1` first.
What does the --yes mode do?
It installs default tools, shared skills and MCP and plugin configuration for the selected agents. The optional catalog of remaining programs is chosen separately or with the `--with-tools` flag.
Can I export changes back to the repository?
Yes, export writes installed configuration back into the repository and sync runs both ways. JSON and other formats are validated before install.
Discussion
No questions or reviews yet.
Related
CLI toolsPersonal assistant kit for Claude Code, Codex CLI and Grok CLI: file-based memory, 23 skills and a guided first-run setup
Set up Claude Code and Codex in one conversation: global instructions, rules, plugins, skills, a status line and correction memory
Local AI commands for voice and text: clipboard dictation, text fixes, speech, an assistant and parallel agents in worktrees
An MCP server and CLI that find in Claude Code and Codex sessions why a file became what it is: who asked the agent what, when and what changed
A CLI that gathers Claude Code and Codex session history into a local graph, searches it and turns repeated mistakes into fixes
A local MCP server for Mac: Claude, Codex and ChatGPT work in apps, files, terminal and browser under your permissions
README in short
The README describes a configuration installer for AI assistants: features, requirements for macOS, Linux, WSL and Windows 11, and safe install through a dry run and a backup. It continues with the `--yes` mode, the default tool list, failure behavior and recovery notes for Windows.