workflow-toolbox
v0.1.0Agents-only shim of the workflow-toolbox plugin, loaded by the observe server into delegated (server-launched) SDK sessions so workflow-toolbox:* agentTypes resolve there despite settingSources: []. Byte-identity-mirrored from plugin/agents/ (launch-agents-identity gate). It ships no context-injecting surfaces and only matcher-narrowed process hooks referenced via ../bin from the parent plugin (no bin/ dir of its own): the verifier-CLI guard on PostToolUse/Bash + PreToolUse/StructuredOutput, and the Path-B envelope-intercept hook on PreToolUse/Agent for workflow-toolbox:opencode-verifier. EVERY OTHER agent (leaf/lean/etc.) runs effectively bare: the hooks spawn only on their matched tools, then self-scope immediately to the narrow bridge case they own. Not for interactive install — the full workflow-toolbox plugin already provides these agents + hooks.
By Frederic Thomas1 GitHub starsUpdated 5 days ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 0 skill or MCP entries
- Source updated
- Sep 18, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install workflow-toolbox for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install workflow-toolbox-2@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/home-dev-lab/workflow-toolboxClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugin/launch-agents/.
Plugin files
└── .claude-plugin/plugin.json
Plugin manifests1
{
"name": "workflow-toolbox",
"version": "0.1.0",
"author": {
"name": "Frederic Thomas",
"email": "[email protected]"
},
"description": "Agents-only shim of the workflow-toolbox plugin, loaded by the observe server into delegated (server-launched) SDK sessions so workflow-toolbox:* agentTypes resolve there despite settingSources: []. Byte-identity-mirrored from plugin/agents/ (launch-agents-identity gate). It ships no context-injecting surfaces and only matcher-narrowed process hooks referenced via ../bin from the parent plugin (no bin/ dir of its own): the verifier-CLI guard on PostToolUse/Bash + PreToolUse/StructuredOutput, and the Path-B envelope-intercept hook on PreToolUse/Agent for workflow-toolbox:opencode-verifier. EVERY OTHER agent (leaf/lean/etc.) runs effectively bare: the hooks spawn only on their matched tools, then self-scope immediately to the narrow bridge case they own. Not for interactive install — the full workflow-toolbox plugin already provides these agents + hooks.",
"hooks": {
"PreToolUse": [
{
"matcher": "Agent",
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/../bin/wt-envelope-intercept-hook.mjs\"",
"timeout": 610
}
]
},
{
"matcher": "StructuredOutput",
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/../bin/wt-verifier-cli-guard-hook.mjs\""
}
]
}
],
"PostToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/../bin/wt-verifier-cli-guard-hook.mjs\""
}
]
}
]
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[workflow-toolbox on Agent Plugins Marketplace](https://pluginsmp.com/plugins/workflow-toolbox-2)