harness-integration-stinger — Claude Code and Codex skill
harness-integration-stinger — a skill for Claude Code and Codex that explains how to wire a single capability—skill, agent, hook, or MCP server—across four platforms: Claude Code, Cursor, Codex, and Cowork.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install wasp-nest-core@wasp-nestWhat harness-integration-stinger does
harness-integration-stinger encodes the process of connecting one capability to four platforms at once. Instead of rebuilding the integration four times, you follow a single playbook: pick a component type, decide how to wire it, verify that each platform supports it, and if not—switch to an alternative without losing functionality.
The skill includes 14 guides, from selecting a component type through checking its support on each platform to shipping through each marketplace. It walks through a full worked example: how Hivemind was ported to six hosts with all decisions answered end to end. That means you do not guess how to handle hooks in Codex when Claude Code supports them—the skill describes how to degrade gracefully.
One critical rule: inspect the actual platform before you design. A cache file and examples from another project do not prove a component is there. The skill teaches you to read each platform's live plugin registry and load resources through its official root, not by assuming a previous product's file layout.
What it helps with
- wire a skill to Claude Code, Cursor, Codex, and Cowork without rewriting it
- find where each component type lives on each platform
- port an agent while keeping its command names and contract intact
- degrade a hook gracefully on a platform that does not support it
- register an MCP server across marketplaces without config conflicts
Example prompts for the agent
- Show me how to register an MCP server in Claude Code and Codex without config clashes
- Give me a table: where skills, rules and hooks live on each platform
- Help me port an agent from Claude Code to Cowork so it runs the same commands
How to install harness-integration-stinger
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install wasp-nest-core@wasp-nestThis installs the whole wasp-nest-core plugin with all its skills
2Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill harness-integration-stinger -a claude-code3Manually: put the files in place
~/.claude/skills/harness-integration-stinger/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/harness-integration-stinger/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill harness-integration-stinger -a codex2Manually: put the files in place
.agents/skills/harness-integration-stinger/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill harness-integration-stinger -a cursor2Manually: put the files in place
.cursor/skills/harness-integration-stinger/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/wasp-nest-core/skills/harness-integration-stinger2Manually: put the files in place
.github/skills/harness-integration-stinger/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill harness-integration-stinger -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/wasp-nest-core/skills/harness-integration-stingerManually: put the files in place
.devin/skills/harness-integration-stinger/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about harness-integration-stinger
How do I install harness-integration-stinger in Claude Code?
Run four commands in order: /plugin marketplace add legioncodeinc/vibe-coding-tools, /plugin install wasp-nest-core@wasp-nest, npx skills add legioncodeinc/vibe-coding-tools --skill harness-integration-stinger -a claude-code, then open ~/.claude/skills/harness-integration-stinger/SKILL.md.
What does harness-integration-stinger do?
It contains 14 guides for porting components between Claude Code, Cursor, Codex, and Cowork. It helps you pick a component type, verify platform support, degrade features on platforms that lack them, and ship through each marketplace.
Why does MCP registration differ between platforms?
Codex reads TOML in mcp_servers; Claude Code and Cursor use JSON. A config copied from one platform will not work on another. The MCP registration guide shows both formats.