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 wdzhwsh4067/supervise-loopnpx agentmods add plugins/wdzhwsh4067/supervise-loop/plugingit clone --depth 1 https://github.com/wdzhwsh4067/supervise-loopGrade A, and why
supervise-loop 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
{
"name": "supervise-loop",
"version": "0.1.0",
"description": "Autonomous supervisor/worker/critic iteration loop for Claude Code (the evaluator-optimizer pattern). Delegate a goal once; a supervisor agent grades each round against a checkable rubric — mechanical checks plus a SEPARATE critic sub-agent — and re-dispatches with feedback until the rubric passes or a hard cap is hit. No human in the loop.",
"author": {
"name": "王少煌",
"email": "[email protected]"
},
"repository": "https://github.com/wdzhwsh4067/supervise-loop",
"license": "MIT",
"keywords": [
"claude",
"claude-code",
"claude-code-plugin",
"claude-skills",
"agent",
"multi-agent",
"orchestration",
"evaluator-optimizer",
"orchestrator-workers",
"supervisor",
"critic",
"agent-loop",
"autonomous-agents"
],
"homepage": "https://github.com/wdzhwsh4067/supervise-loop#readme"
}
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 · 28 lines scan A 98e511c36613
supervise-loop is a plugin published in the GitHub repository wdzhwsh4067/supervise-loop (1 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
agentsys
26 specialized plugins for AI workflow automation - task orchestration, PR workflow, slop detection, code review, drift detection, enhancement analysis, documentation sync, unified static analysis, durable memory, negative behavior memory, skill and system prompt curation, perf investigations, topic research, agent…
agentsys
Professional-grade slash commands for Claude Code with cross-platform support.
no-human-ai
The nohuman plugin for Claude Code: hand a task to your local nohuman and check on it without leaving the session.
no-human
File a task with nohuman and check on it without leaving Claude Code: taskadd and taskstatus over your local nohuman server (127.0.0.1:8420). nohuman plans, codes, tests and has the work reviewed by a second model, then opens the pull request and stops.
goal-mode
Better Goal — long-horizon autonomous mode for Claude Code: hierarchical plan-tree with acceptance criteria, review-gates, and triple budget. Codex /goal analog.
goal-mode
Better Goal — long-horizon autonomous mode for Claude Code: hierarchical plan-tree (Sprint→Epic→Task) with acceptance criteria, review-gates, and a triple budget. Codex /goal analog.