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 instructions/procoders/superpowers-v/gemini-mdgit clone --depth 1 https://github.com/procoders/superpowers-vWhat 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.02170 | $0.02170 |
| Opus 5 | $0.01085 | $0.01085 |
| Sonnet 5 | $0.00434 | $0.00434 |
| Haiku 4.5 | $0.00217 | $0.00217 |
Grade A, and why
superpowers-v GEMINI.md 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compound V — Gemini CLI Shim (🧪 experimental, untested)
This file documents how the plugin's content would be used in Gemini CLI. The shim has not been tested on a real Gemini CLI install — the manifest format for Gemini CLI extensions is version-specific and the maintainer has not verified compatibility. Treat this as a starting point, not a working integration.
What this plugin does
Compound V is a sidekick to Superpowers. It intercepts the four Superpowers phase transitions (pre-brainstorm recon → brainstorming → writing-plans → execution) and adds:
- Gated pre-brainstorm recon (Trigger 0) 🧪 description-driven, with a reminder-only hook backstop (
hooks/brainstorm-trigger0-nudge.sh, a Claude Code hook that nudges when the Skill tool invokessuperpowers:brainstorming— a reminder, not enforcement): before a brainstorm begins on an unfamiliar topic, a gated, bounded research pass (bundleddeep-researchif present, 3–6 parallel WebSearch otherwise, skip-with-notice if neither) writes an anti-anchoring recon doc todocs/superpowers/recon/that the brainstorm — and later pre-flights 1B/1C — read first. Gate order: plumbing-skip → V-memory KB hit →brainstorm.deep_researchconfig (askdefault /auto/offhard kill-switch). Recon is evidence, never a routing input. Also 🧪 description-driven: batched elicitation — ≥3 independent clarifying questions may batch into ONE screen via the surface ladder — Visual Companion form if accepted this session, else the harness's structured-question tool, else sequential (companion acceptance gates only the top surface); dependent chains stay sequential; when unsure → sequential; seeskills/compound-v/brainstorm-elicitation.md. - Three parallel pre-flights after brainstorming:
- Code archaeology (existing-code reality)
- Domain-expert advisor with three-layer audience search (product/regulatory reality)
- Library/doc validator via Context7 MCP (dependency currency)
- Disjoint File Partition Map enforcement inside writing-plans, which materializes a
manifest.yaml— the machine-readable contract that drives dispatch - Manifest-driven dispatch on the most capable model available (Gemini 3.1 Pro or equivalent), with a
git diffscope gate after every job (a worker that writes outside itswrite_allowedlist is BLOCKED and never merges) and crash-resume via astate.jsonrun directory
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 · 89 lines · 2,170 tokens per session scan A efca0856fa36
superpowers-v GEMINI.md is an instructions file published in the GitHub repository procoders/superpowers-v (35 stars, last pushed 2d ago), licensed MIT. It adds 2,170 tokens to every session, about $0.0109 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 instructions, from other repositories
harness-anchor CLAUDE.md
Instructions for Redtropig/harness-anchor, covering harness-anchor — contributor & ai collaborator guidelines, if you are an ai agent editing this plugin, design invariants (do not break), shell hazards no tool in this repo catches and authoring a new skill (when explicitly asked).
forge-orchestrator CLAUDE.md
Claude Code instructions for tarunms7/forge-orchestrator, covering workflow orchestration, 1. plan mode default, 2. subagent strategy, 3. self-improvement loop and 4. verification before done.
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
entroly CLAUDE.md
Instructions for juyterman1000/entroly, covering claude.md, gstack operating protocol, default workflow, entroly trust invariants and review checklist.
autonomous-os AGENTS.md
Instructions for autonomous-ai/autonomous-os, covering agents.md, multi-ide rules, working style, parallel work / subagents and device access rules.
spellbook AGENTS.md
Instructions for majiayu000/spellbook, covering spellbook agent contract, routing, scope rules, threads long-run guardrails and validation.