This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
agent-harness
The missing package manager for MCP servers and AI skills
Stop managing AI agent assets by hand. agent-harness discovers MCP servers, skills, and rules from trusted sources; pins and mirrors them reproducibly; quarantines risky inputs; then wires everything into Cursor, Claude Code, Copilot, Zed, Codex, OpenCode and Pi.
Hey PH 👋 — I'm Ahmed, the solo developer behind agent-harness.
The problem I kept hitting: every AI editor has its own file layout, its own rules format, and its own way of consuming MCP servers and skills. I'd wire up Cursor, then rebuild everything from scratch for Claude Code, then again for Copilot. And not to mention the differences in agent assets required based on the project stack and session intent. There was no reproducible middle layer — just scattered files and hope.
agent-harness is that middle layer. One CLI that discovers agent assets from trusted sources, pins and mirrors them locally, quarantines anything that looks like a prompt-injection risk, and wires the result into whichever editor you're in — Cursor, Claude Code, VS Code/Copilot, Zed, OpenCode, Pi, or Codex.
Three things I built that I haven't seen elsewhere: → A quarantine + audit trail for risky assets (no silent installs) → Preview-first wire-in with explicit apply/reset — no mystery files → ARD-compatible (v1.0 spec, announced by Google + Microsoft) as both publisher and consumer
v2.1.0 ships today on npm: npm install -g @ar27111994/agent-harness agent-harness workspace opencode --intent general
Happy to answer any questions — especially about host-specific wiring, the quarantine model, or ARD integration plans for > v2.1. What editor are you running?
No comment highlights available yet. Please check back later!
About agent-harness on Product Hunt
“The missing package manager for MCP servers and AI skills”
agent-harness was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #83 on the daily leaderboard. Stop managing AI agent assets by hand. agent-harness discovers MCP servers, skills, and rules from trusted sources; pins and mirrors them reproducibly; quarantines risky inputs; then wires everything into Cursor, Claude Code, Copilot, Zed, Codex, OpenCode and Pi.
agent-harness was featured in Productivity (661.2k followers), Developer Tools (519.8k followers), Artificial Intelligence (479.1k followers), GitHub (41.4k followers) and YouTube (17k followers) on Product Hunt. Together, these topics include over 403.3k products, making this a competitive space to launch in.
Who hunted agent-harness?
agent-harness was hunted by Ahmed Rehan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how agent-harness stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Ahmed Rehan
Hey PH 👋 — I'm Ahmed, the solo developer behind agent-harness.
The problem I kept hitting: every AI editor has its own file layout, its own rules format, and its own way of consuming MCP servers and skills. I'd wire up Cursor, then rebuild everything from scratch for Claude Code, then again for Copilot. And not to mention the differences in agent assets required based on the project stack and session intent. There was no reproducible middle layer — just scattered files and hope.
agent-harness is that middle layer. One CLI that discovers agent assets from trusted sources, pins and mirrors them locally, quarantines anything that looks like a prompt-injection risk, and wires the result into whichever editor you're in — Cursor, Claude Code, VS Code/Copilot, Zed, OpenCode, Pi, or Codex.
Three things I built that I haven't seen elsewhere:
→ A quarantine + audit trail for risky assets (no silent installs)
→ Preview-first wire-in with explicit apply/reset — no mystery files
→ ARD-compatible (v1.0 spec, announced by Google + Microsoft) as both publisher and consumer
v2.1.0 ships today on npm:
npm install -g @ar27111994/agent-harness
agent-harness workspace opencode --intent general
Full walkthrough: https://youtu.be/u1OmcS97iOg
Happy to answer any questions — especially about host-specific wiring, the quarantine model, or ARD integration plans for > v2.1. What editor are you running?