Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add plugins/harshvardhan86/claude-wave-plugin/marketplace/plugin marketplace add Harshvardhan86/claude-wave-plugingit clone --depth 1 https://github.com/Harshvardhan86/claude-wave-pluginGrade A, and why
claude-wave-plugin scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "claude-wave-plugin",
"description": "Wave-based engineering execution for Claude Code. Vendors the full v2 framework (17 base phases plus conditional [DR] for UI waves and optional [CR] code-review gate) plus a polished 5-phase demo subset for live segments and small UI features.",
"owner": {
"name": "Harshvardhan Singh Chouhan",
"email": "[email protected]"
},
"plugins": [
{
"name": "claude-wave-plugin",
"description": "Run Claude Code like an engineering org. Wave-based execution with dedicated sub-agents per phase, computed-style visual verification, no \"tsc passes\" lies. Vendors the full Wave Execution Framework v2 (17 base phases + conditional [DR] and [CR] gates, max 19) plus a polished 5-phase demo subset for live segments and small UI features.",
"author": {
"name": "Harshvardhan Singh Chouhan",
"email": "[email protected]"
},
"category": "development",
"source": {
"source": "url",
"url": "https://github.com/Harshvardhan86/claude-wave-plugin.git"
},
"homepage": "https://github.com/Harshvardhan86/claude-wave-plugin",
"license": "MIT",
"keywords": [
"tdd",
"orchestration",
"wave-framework",
"design-review",
"visual-verification",
"production-grade",
"agent-frameworks"
]
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 36 lines scan A dbd047921210
claude-wave-plugin is a plugin published in the GitHub repository Harshvardhan86/claude-wave-plugin (8 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
rune-kit
Less skills. Deeper connections. A lean, interconnected skill ecosystem for Claude Code — 66 skills, 248 connections, 45 signals, and runtime auto-discipline.
rune
67-skill mesh for Claude Code with runtime auto-discipline — native hooks (preflight/sentinel/completion-gate/quarantine) auto-fire at lifecycle boundaries. 248 mesh connections + 46 signals, adaptive routing, mesh analytics, MCP quarantine guidance, and project memory.
gaia-marketplace
Security-first multi-agent orchestration for Claude Code. Distributes the Gaia plugin: specialized agents across the development lifecycle with codebase-aware context injection and risk-classified command gating.
relay
Delegate work packets from a lead Claude Code session to executor sessions in their own iTerm tabs, with session reuse instead of always spawning fresh.
specwright
Plugin marketplace listing 1 plugin: specwright.
ac
Main-agent planning trio (/ac:plan, /ac:execute, /ac:wisdom) with autonomous execution mode plus setup, init, commit commands and skill, agent, command, rule, CLAUDE.md creator skills. Two hooks back the workflow: SessionStart for twin-skill and resume, PreCompact for state preservation.