I’ve been building Claude Code plugins for specific workflows. Instead of scattering them across repos, I consolidated them into a single marketplace: claude-tools.

Four plugins. Each delegates to specialized external tools.

The Plugins

Gemini Tools

Visual analysis and UI generation via Gemini 3 Pro.

/gemini:visual review this screenshot for accessibility issues
/gemini:mockup dashboard with dark glassmorphism theme 16:9

Two commands:

  • /gemini:visual: Analyze screenshots, mockups, designs. Get UI/UX feedback, accessibility audits, design pattern suggestions.
  • /gemini:mockup: Generate UI mockups with configurable aspect ratios (1:1, 16:9, 9:16) and resolutions (1K, 2K, 4K).

Why Gemini? State-of-the-art multimodal. It sees what Claude cannot. I wrote about the hybrid workflow previously.

Codex

Architecture thinking via OpenAI Codex.

/codex:review should we use a monorepo or polyrepo?
/codex:review review the authentication architecture

Codex runs as an Opus agent that thinks like a senior engineer: questions assumptions, identifies constraints, analyzes trade-offs. When it needs external research, it delegates to the Codex CLI via haiku subagents.

I wrote about the Codex workflow previously. This plugin packages that pattern.

DNS

Multi-provider DNS management.

/dns:spaceship example.com
/dns:godaddy another-domain.com

Same workflow for both providers: list current records, parse requested changes, batch apply via API. Supports common record types (A, AAAA, CNAME, MX, TXT, NS, SRV, CAA) with built-in examples for Resend, SES, Google Workspace.

Why DNS in a coding plugin?

Domain migrations, email setup, and infrastructure provisioning are common during project work. Having DNS accessible via slash command keeps me in flow.

Headless

Browser automation for site comparison and E2E testing.

/headless:parity https://legacy.example.com https://migrated.example.com
/headless:test https://example.com "Test login, checkout, and profile flows"

Two commands:

  • /headless:parity: Compare legacy vs migrated sites during framework migrations. Spawns parallel agents testing both sites side-by-side.
  • /headless:test: AI-driven E2E testing. Describe flows and expected behavior, agents validate with screenshots.

Both spawn parallel Playwright browser agents:

Running 4 headless:parity-browser agents...
├─ Parity: Homepage · 34 tool uses · 33.4k tokens
├─ Parity: Terms page · 19 tool uses · 21.0k tokens
├─ Parity: Login page · 46 tool uses · 57.5k tokens
└─ Parity: Dashboard page · 24 tool uses · 28.2k tokens

Each agent captures screenshots, compares states, reports differences with severity. The orchestrator aggregates results into a health assessment.

The Architecture Pattern

All plugins follow the same pattern: Claude orchestrates, external tools execute.

Slash command → Agent → Subagent (haiku) → External tool

Why subagents? Token isolation. The Gemini API call, Codex CLI execution, browser automation: these generate verbose output that would bloat Claude’s context. Delegating to haiku subagents keeps costs low and the main session clean.

Don’t make Claude do everything. Make Claude coordinate the right tools for each job.

Headless + Ralph Wiggum

Combine Headless with ralph-wiggum for continuous validation:

/ralph-wiggum:ralph-loop "Run /headless:parity https://legacy.example.com https://migrated.example.com, then fix any differences found in the migrated site" --max-iterations 20 --completion-promise "All pages pass parity check"

Each iteration runs the parity check, then fixes any differences found. The loop continues until all pages pass or iterations exhaust.

For large migrations, this becomes your overnight CI: push fixes, let the loop validate, wake up to a status report.

Token cost

Headless browser agents run on haiku, so token costs are minimal despite the 20-60k tokens per agent. The parallelism is cheap.

Installation

# Add the marketplace
claude plugin marketplace add paddo/claude-tools

# Install what you need
claude plugin install gemini-tools@paddo-tools
claude plugin install codex@paddo-tools
claude plugin install dns@paddo-tools
claude plugin install headless@paddo-tools

Each plugin has dependencies documented in its README. Gemini needs gemini-cli and pngpaste. Codex needs @openai/codex. Headless auto-installs Playwright on first run.

What This Isn’t

These plugins don’t replace Claude’s core capabilities. They extend Claude with specialized external tools for specific workflows:

  • Visual analysis that requires seeing images
  • Architecture thinking from a different AI perspective
  • Browser automation that needs real browser sessions
  • API integrations for external services
Build your own

The plugin structure is simple: markdown agents with YAML frontmatter, slash commands that delegate to agents, and optional library code for complex operations. Clone the repo, copy a plugin, modify for your workflow.

The marketplace is open. Star the repo if it’s useful. PRs welcome.

Related Posts