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 andyzengmath/quantum-loopnpx agentmods add plugins/andyzengmath/quantum-loop/marketplacegit clone --depth 1 https://github.com/andyzengmath/quantum-loopGrade A, and why
quantum-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 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": "quantum-loop",
"owner": {
"name": "andyzengmath"
},
"metadata": {
"description": "Universal CLI orchestrator with multi-runner support. Autonomous spec-driven development pipeline with dependency DAG, parallel worktree execution, two-stage review gates, DAG intelligence validation, and modular merge hardening",
"version": "0.11.5"
},
"plugins": [
{
"name": "quantum-loop",
"source": "./",
"description": "6 skills (brainstorm, spec, plan, execute, verify, review) and 5 agents for autonomous spec-driven development with multi-runner support, DAG intelligence, and modular merge hardening",
"version": "0.11.5",
"keywords": [
"autonomous",
"prd",
"tdd",
"verification",
"review",
"planning",
"agent-loop",
"multi-runner",
"codex",
"copilot",
"gemini",
"universal-orchestrator"
],
"category": "productivity"
}
]
}
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.
- 2d ago First seen · 34 lines scan A 442332932c5f
quantum-loop is a plugin published in the GitHub repository andyzengmath/quantum-loop (24 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-30.
Other plugins, from other repositories
token-optimizer
Plugin marketplace listing 3 plugins: token-optimizer, to-hook-probe, token-optimizer-cowork.
token-optimizer
Audit, fix, and monitor Claude Code context window usage. Find the ghost tokens.
to-hook-probe
nord-electro-6
Manage program presets on a Nord Electro 6 keyboard over USB.
lattice
A marketplace of composable AI skills covering the full software delivery lifecycle — from requirements and design through implementation, testing, and review. Each plugin targets a specific SDLC role: backend engineers, frontend engineers, QA, business analysts, and more.
firecrawl-lean
Plugin marketplace listing 1 plugin: firecrawl-lean.