superscalar

superscalar is a plugin for Claude Code from SoliEstre/EstreGenesis. Its manifest loads nothing; the 5 skills it bundles cost 889 tokens per session together, scanned A, original, Apache-2.0.

A scheduling discipline for sending separate coding tasks to multiple agents at once. It also controls when an agent may speculate, while keeping writes, deployments, messages, and deletions outside that permission.

In plain words
What is it for?
Use it to coordinate parallel agent tasks, set speculation approval, stop speculative work, and record incorrect predictions.
Why use it?
It makes parallel work easier to control and shows when a task was started on an assumption that later proved wrong.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add SoliEstre/EstreGenesis
agentmods
npx agentmods add plugins/soliestre/estregenesis/superscalar
Clone the repo
git clone --depth 1 https://github.com/SoliEstre/EstreGenesis

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for superscalar

README.md
[![agentmods](https://agentmods.dev/badge/plugins/soliestre/estregenesis/superscalar.svg)](https://agentmods.dev/plugins/soliestre/estregenesis/superscalar)
Your own site
<a href="https://agentmods.dev/plugins/soliestre/estregenesis/superscalar"><img src="https://agentmods.dev/badge/plugins/soliestre/estregenesis/superscalar.svg" alt="Measured on agentmods" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 5 skills cost 889 tokens a session between them.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

superscalar 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 4d 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.

plugins/superscalar/.claude-plugin/plugin.json · 13 lines

How it starts

The opening of the file, as written. The whole thing — 13 lines — stays where its author put it; the contents beside it link to each section on GitHub.

{
  "name": "superscalar",
  "version": "0.5.0",
  "description": "Execution-scheduling discipline for parallel sub-agent dispatch. v0.5.0 / Superscalar v0.14.0 adds the /speculation toggle (§4 speculation authorization) — four modes plus a read-back (off default / auto asks per speculation with the four-element trade-off / on pre-authorizes low-downstream-sensitivity lanes while high-sensitivity ones still ask / always pre-authorizes every lane inside the §3 barrier / status reports the mode and where it would next apply). The modes graduate along downstream sensitivity, an axis §4 already named, so this is a threshold on existing vocabulary rather than new vocabulary. One constraint governs all four and cannot be read past: the mode changes WHO authorizes a lane, never WHAT a lane may touch — read the other way, there is no mode in which speculation reaches a write, deploy, send, or delete, so no operator setting turns speculation into an outward-facing action; widening scope is a separate and narrower decision than changing who signs off. Andon transparency (visual signal, /stop-spec pull-cord, misprediction logging) is unconditional at every mode including always, because pre-authorization removes the question and not the visibility — dropping the announcement at always would make the loudest mode the quietest one. State is one marker (.agent/speculation.json, absent ⇒ off) read at dispatch time and never mirrored, and a mode change is a declaration event where a board is present. v0.4.0 / Superscalar v0.12.0 adds the /context-caching toggle (§5.4 memory-hierarchy borrowing) — three modes (off/self/agent): pin model+effort at session head (each is a cache key), compact at task boundaries with rewind-over-compact for abandoned paths, prefetch context right after boundaries, account for cache-cold subagents in fan-out pricing, consult the per-harness flush list before mid-session mutations, and measure with the cache counters instead of declaring; volatile vendor 

Read the full file on GitHub · 13 lines

Contents

What it installs

The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 889 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Changes

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.

  1. 4d ago First seen · 13 lines scan A 4b1a69f18430

Subscribe to this mod's changes

superscalar is a plugin published in the GitHub repository SoliEstre/EstreGenesis (8 stars, last pushed 10d ago), 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-31.