Claude Tools

claude-tools

Shared plugins for Claude Code and Codex.
Both hosts use the same skills, references, and helper scripts.
See release notes and plugin versions.

Install

Run these commands from this checkout. Replace cc with the required plugin name.

For GitHub installation, use paddo/claude-tools instead of . as the marketplace source.
Both marketplaces use the name paddo-tools.

Plugins

Claude Code exposes skills as /plugin:skill, such as /dns:spaceship or /cc:review.
Claude agents use the same form, such as the cc:review agent.
In Codex, use /skills or $ to select a skill from its plugin.
Natural-language requests also work, such as “Use Grok to review these changes.”

Requirements

Use a local host with shell access and the tools required by the selected plugin.

Credentials

The plugins read each API credential from the environment first, then from the macOS keychain.
Keychain storage keeps secrets out of shell profiles, and desktop apps do not need to inherit them.
Store each credential under the paddo-tools service. The command prompts for the value:

On other systems, export the variables before you start either host.
The Codex sandbox blocks keychain reads and network access. Approve these commands to run outside it.

Scout uses direct retrieval without a paid key. SCOUT_MAX_CREDITS sets its shared budget limit.
External review CLIs use their own configured accounts and models.

Structure

Each plugin has .claude-plugin/plugin.json, .codex-plugin/plugin.json, and skills//SKILL.md.
Claude agents load those skills through the plugin root path. Codex uses the skills directly.
Helper paths resolve from the installed skill or reference file, independent of either host's cache directory.
Browser workflows use available host subagents for independent flows. Mobile…