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.
/plugin marketplace add derricktang/pm-workflow-pluginnpx agentmods add plugins/derricktang/pm-workflow-plugin/marketplacegit clone --depth 1 https://github.com/derricktang/pm-workflow-pluginGrade A, and why
pm-workflow-market 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 2d ago.
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
{
"name": "pm-workflow-market",
"displayName": "PM Workflow Marketplace",
"description": "AI 产品经理工作流插件市场",
"version": "1.0.0",
"author": { "name": "derricktang" },
"plugins": [
{
"name": "pm",
"displayName": "PM Workflow",
"description": "结构化 AI 产品经理工作流",
"source": "./plugins/pm"
}
]
}
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.
- 2d ago First seen · 16 lines scan A b22593487aed
pm-workflow-market is a plugin published in the GitHub repository derricktang/pm-workflow-plugin (2 stars, last pushed 2mo 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
better-harness
Build an AI-ready engineering system for safe coding-agent delivery and continuous software improvement.
claude
Connect Claude Code to your local OpenLoomi runtime. One-command install, mirror Claude's lifecycle onto the Loomi Pet, and auto-archive every Stop into your OpenLoomi memory. Talks to your local OpenLoomi over HTTP and the OpenLoomi helper CLI. AI provider config is owned by OpenLoomi itself — this plugin never reads.
sd0x-harness
Harness engineering for Claude Code — reminder-layer review hooks, behaviour-layer gates, and fail-closed safety where it counts.
mumei
mumei marketplace (single-plugin, self-hosted).
agent-harness
Multi-agent harness for Claude Code: Planner→Generator→Evaluator sprints executed as background dynamic workflows (Agent-tool fallback), fable/opus/sonnet/haiku model routing with per-role reasoning effort, harness-engineering framework for design/diagnosis, and Anthropic 2026-04-04 P-G-E pattern.
ratchet
Torque Loop turns ambiguous work into shipped artifacts through target locking, adversarial validation, patching, and state serialization — plus a bounded /ratchet:evolve loop. A stateful advancement engine, not a prompt library. Not affiliated with Anthropic.