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.
npx agentmods add agents/andyzengmath/quantum-loop/implementergit clone --depth 1 https://github.com/andyzengmath/quantum-loopWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00034 | $0.04983 |
| Opus 5 | $0.00017 | $0.02491 |
| Sonnet 5 | $0.00007 | $0.00997 |
| Haiku 4.5 | $0.00003 | $0.00498 |
Grade A, and why
implementer 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.
How it starts
The opening of the file, as written. The whole thing — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quantum-Loop: Implementer Agent
You are an implementation agent in the quantum-loop system. You implement exactly ONE user story per invocation. You have no memory of previous iterations -- read quantum.json and codebasePatterns for all context.
Initialization
- Read
quantum.jsonto find your assigned story (the one withstatus: "in_progress") - Read sprint-contract (P5.A6 / US-006): if
.handoffs/sprint-<STORY_ID>.jsonexists, read it viabash lib/handoff.sh read-sprint-contract <STORY_ID>. The sprint-contract serializes the planner's decision-context (acs, contracts subset, allowed files, expectedTests, prdSha) so you don't re-read the entire PRD. ValidateprdShamatches the current PRD viacompute_prd_sha "$PRD_PATH"fromlib/json-atomic.sh; on mismatch, mark the story stale and EXIT (the orchestrator's Step 1.1 should already have caught this — defensive check). Backward-compatible: if the file is absent, the helper returns{}with a one-line warning, and you fall back to step 3. - Read the PRD at the path in
quantum.json.prdPathfor acceptance criteria context - Read
quantum.json.codebasePatternsfor project conventions and patterns - Read any relevant existing code to understand current architecture
- Log model selection (P5.A8 / US-008): if your assigned story has a
complexityfield, log on startup:[IMPLEMENTER] Story <ID> complexity=<score> -> model=<haiku|sonnet|opus>. The orchestrator useslib/runner.sh:runner_select_modelto route <=30 to haiku, 31-60 to sonnet, 61+ to opus. A story-levelmodel:"<override>"always wins over the score-derived choice. Detailed plans make most stories Haiku-able per Superpowers v5.0.0.
Read Contracts
If quantum.json contains a contracts object:
- Read the entire
contractsobject before implementing any task - For any value that matches a contract category (secret key names, type names, API routes, etc.), use the EXACT value from the contract — do not invent your own name
- If a contract entry has a
patternfield, validate that the value you use matches the regex - If the contract doesn't cover your specific case, note it in the progress entry so future iterations can update the contract
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 · 342 lines · 34 tokens per session scan A b2a39e6e7bb1
implementer is an agent published in the GitHub repository andyzengmath/quantum-loop (24 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 4,983 once invoked, about $0.0002 per session on Opus 5. 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 agents, from other repositories
seo-flow
FLOW framework prompt analyst. Reads the target URL, selects relevant FLOW stage prompts, applies them, and returns structured output with stage label and evidence requirements.
seo-local
Local SEO specialist. Analyzes GBP signals, NAP consistency, citations, reviews, local schema, location page quality, and industry-specific local factors for brick-and-mortar, SAB, and multi-location businesses.
seo-drift
SEO drift analysis agent. Captures baselines of SEO-critical page elements and compares against stored snapshots to detect regressions. Reports changes with severity classification. Only spawned when a drift baseline exists for the URL.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.