superconductor

superconductor is a skill for Claude Code, Codex from HazAT/pi-config. It costs 53 tokens per session (1,384 once invoked), scanned A, original, MIT.

A guide for using the Superconductor command-line tool to manage app-run coding agents, teams, sessions, layouts, worktrees, and review threads. A worktree is a separate working copy of a Git repository.

In plain words
What is it for?
Use it when a workflow explicitly requires Superconductor to start or coordinate agents, manage sessions or views, create worktrees, or handle review threads.
Why use it?
It provides the required checks and safety rules for changing agent sessions, repository workspaces, or in-app review state. It also requires verifying that an operation actually finished.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

Good fit Use it when a workflow explicitly requires Superconductor to start or coordinate…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hazat/pi-config/superconductor
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.

Any agent
npx skills add HazAT/pi-config --skill superconductor
Clone the repo
git clone --depth 1 https://github.com/HazAT/pi-config

Made for: Claude Code, Codex.

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 superconductor

README.md
[![agentmods](https://agentmods.dev/badge/skills/hazat/pi-config/superconductor.svg)](https://agentmods.dev/skills/hazat/pi-config/superconductor)
Your own site
<a href="https://agentmods.dev/skills/hazat/pi-config/superconductor"><img src="https://agentmods.dev/badge/skills/hazat/pi-config/superconductor.svg" alt="Measured on agentmods" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,384 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.01384
Opus 5 $0.00026 $0.00692
Sonnet 5 $0.00011 $0.00277
Haiku 4.5 $0.00005 $0.00138

Measured 7d ago against content hash b511c64eb41f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

superconductor 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 7d 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.

skills/superconductor/SKILL.md · 117 lines

How it starts

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

Superconductor CLI

Use live sc instructions and capability output as authoritative. Keep SC syntax and lifecycle policy here; role skills should reference this skill rather than reproduce commands.

Boundaries

  • Use SC only for the requested orchestration or app-managed outcome.
  • Require explicit human intent for worktree/branch creation or deletion, target-branch changes, force termination, destructive cleanup, closing/rearranging existing sessions, and unrelated review-thread mutations.
  • Never create a worktree merely for delegation or launch replacement agents for follow-ups.
  • Prefer stable labels or stable target IDs and --active keep.
  • Dispatch and idle state are not completion; always wait, read, and verify.

Live Preflight

Before the first mutation, run the matching guide:

Area Command
Agents, teams, delegation sc instructions orchestration
Tabs, panes, views sc instructions layout
Worktrees or branches sc instructions worktree
In-app review threads sc instructions review

For orchestration, inspect current capabilities and targets:

command -v sc
sc layout capabilities --output json
sc layout views --worktree "$PWD" --output json
sc agents list --worktree "$PWD" --output json
sc chat providers --json

Verify the launch shape, provider, UI mode, model, reasoning level, and structured-read support before specifying them. If unavailable, report the exact limitation instead of silently substituting another mechanism.

Read references/orchestration.md before launching or controlling sessions. Read references/worktrees-and-reviews.md before requested worktree or review-thread operations.

Individual Pi Worker

Delegated Pi sessions default to terminal mode. Long prompts should use a temporary JSONL launch input built with jq; it is command input, not durable workflow state, and must be removed after launch.

sc layout run tabs \
  --provider pi --ui terminal \
  --label worker-TODO-001 \
  --prompt 'Complete prompt with task and absolute handover paths.' \
  --worktree "$PWD" --active keep --output json

Read the full file on GitHub · 117 lines

Files

What ships with it

2 files beside SKILL.md 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.

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. 7d ago First seen · 117 lines · 53 tokens per session scan A b511c64eb41f

Subscribe to this mod's changes

superconductor is a skill published in the GitHub repository HazAT/pi-config (443 stars, last pushed 12d ago), licensed MIT. It adds 53 tokens to every session and 1,384 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

codex-autoresearch

Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…

leo-lilinxiao/codex-autoresearch · 80 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens