spec-superflow AGENTS.md

A set of instructions and tools for a Codex plugin that combines OpenSpec-style planning with a disciplined implementation process. It includes TypeScript build, test, and validation commands.

In plain words
What is it for?
Use it when building the plugin, running integration tests, testing one case, or validating its generated artifacts.
Why use it?
It explains how the plugin is organized and how to verify changes across the supported installation environments.

Instructions file for CodexOpenCode

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.

agentmods
npx agentmods add instructions/magebyte-zero/spec-superflow/agents-md
Clone the repo
git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow

Made for: Codex, OpenCode.

Per session 1,810 This file is loaded in full into every session.
When invoked 1,810 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.01810 $0.01810
Opus 5 $0.00905 $0.00905
Sonnet 5 $0.00362 $0.00362
Haiku 4.5 $0.00181 $0.00181

Measured yesterday against content hash 95ba03d9aaae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-superflow AGENTS.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 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.

AGENTS.md · 140 lines

How it starts

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

AGENTS.md

This file provides guidance to Codex (codex.ai) when working with code in this repository.

What This Is

A self-contained Codex plugin that integrates OpenSpec-style planning + Superpowers execution discipline. Zero runtime dependencies, supports 9 installation surfaces (Claude Code, Cursor, OpenAI Codex CLI, OpenAI Codex App, GitHub Copilot CLI, Gemini CLI, OpenCode, WorkBuddy, Trae).

Commands

# Build TypeScript
npm run build

# Run integration tests
npm test

# Run single test (Node 20+ native test runner)
node --test tests/e2e.test.mjs --test-name-pattern="parseDeltaSpec"

# Validate artifacts (uses docs/examples/ data)
npm run validate

Architecture

Source Code (src/)

TypeScript interfaces + regex-based parsers. Compiles to dist/ (ES2022 + NodeNext + strict).

  • schema/ — Type definitions: base.ts (Requirement, Scenario), change.ts (Delta operations), spec.ts
  • parsing/requirement-blocks.ts parses delta spec markdown. change-parser.ts extracts ## Why + ## What Changes + delta sections from proposal markdown.
  • validation/validator.ts validates artifacts against schema rules. constants.ts holds thresholds. All public API re-exported from src/index.ts.

Validation Rules

  • spec.md: Each Requirement must contain SHALL or MUST, at least 1 #### Scenario: block
  • Delta spec: ADDED/MODIFIED must have requirement text + scenarios; cross-section conflicts blocked
  • proposal.md: ## Why ≥ 50 characters, ## What Changes cannot be empty
  • Validator returns ValidationReport with {valid, issues: [{level, path, message}], summary}. Strict mode treats warnings as errors.

Skills (skills/)

9 skills, one per directory. Each contains a SKILL.md that Codex loads as an instruction set:

Skill Phase Purpose
workflow-start Entry Content-level state detection, 8-state routing, blocks illegal transitions
need-explorer Exploring One-question-at-a-time elicitation, 2-3 approach comparison with recommendation
spec-writer Specifying Generate planning artifacts + Schema engine validation
contract-builder Bridging Parsing engine auto-extracts 4 planning artifacts → compresses into execution-contract.md
build-executor Executing TDD Iron Law + SDD subagent-driven development + Review Gates
bug-investigator Debugging 4-phase root cause analysis. 3+ fix failures → question architecture → escalate
code-reviewer Review Structured review with 3 severity levels (Critical/Important/Minor)
release-archivist Closing Verification-before-completion Iron Law, archiving, risk summary
spec-merger Sync Delta Spec → intelligent merge into main specs, conflict detection

Read the full file on GitHub · 140 lines

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. yesterday First seen · 140 lines · 1,810 tokens per session scan A 95ba03d9aaae

Subscribe to this mod's changes

spec-superflow AGENTS.md is an instructions file published in the GitHub repository MageByte-Zero/spec-superflow (776 stars, last pushed 3d ago), licensed MIT. It adds 1,810 tokens to every session, about $0.0090 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.