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 huangruiteng/loopxnpx agentmods add plugins/huangruiteng/loopx/claude_goal_modegit clone --depth 1 https://github.com/huangruiteng/loopxGrade A, and why
loopx-goal-mode 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": "loopx-goal-mode",
"version": "0.1.0",
"description": "LoopX adapter for Claude Code: the loopx control-plane MCP (should_run / claim_task / complete_task) + the /loopx setup command + statusline. The run loop is Claude Code's native /loop, driven by a .claude/loop.md that /loopx writes; the optional should_run PreToolUse gate (hooks/goal_policy.py) is added deliberately via install.py --harden, NOT by default.",
"author": "loopx",
"commands": "./commands",
"statusLine": {
"type": "command",
"command": "python3 \"${CLAUDE_PLUGIN_ROOT}/statusline/goal_status.py\""
},
"mcpServers": {
"loopx": {
"command": "python3",
"args": ["${CLAUDE_PLUGIN_ROOT}/mcp/loopx_mcp.py"]
}
}
}
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 · 18 lines scan A ab79220a20b5
loopx-goal-mode is a plugin published in the GitHub repository huangruiteng/loopx (5,394 stars, last pushed today), licensed Apache-2.0. 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-30.
Other plugins, from other repositories
agent-triforce
Multi-agent development system with three specialized agents (PM, Dev, QA) coordinated through checklist methodology based on The Checklist Manifesto and Boeing's checklist engineering.
hyperflow
Point it at a GitHub issue and get back a reviewed pull request. Hyperflow turns one AI coding session into a structured engineering pipeline: plan sharpens and decomposes the work, dispatch fans out parallel workers, and a domain specialist reviews every step — nothing ships unreviewed. 18 skills, 22 specialist…
agency-os
Run your work like an AI agency, from a single Notion board. Agents discuss, plan, and execute tasks in parallel with dependency ordering and model routing.
flow-next
Zero-dependency, spec-driven agentic SDLC: durable specs, context-fit plans, re-anchored workers, adversarial cross-model review, and receipts. Includes 20 subagents, 29 commands, 33 skills.
wmux-orchestrator
Multi-agent task orchestration with visual terminal panes. Decomposes complex dev tasks into parallel Claude Code instances coordinated through dependency-aware waves.
genie
Human-AI partnership for Claude Code. Share a terminal, orchestrate workers, evolve together. Brainstorm ideas, turn them into wishes, execute with /work, validate with /review, and ship as one team.