ultrapowers: Instructions file for Codex

AGENTS.md

ultrapowers AGENTS.md is an instructions file for Codex, OpenCode from 7xuanlu/ultrapowers. It costs 1,620 tokens per session, scanned A, original, MIT.

Repository instructions for Ultrapowers, a workflow that coordinates coding tasks through planning, implementation, tests, reviews, and fixes. TDD means writing a failing test before the code that makes it pass.

In plain words
What is it for?
Use them when contributing to Ultrapowers, changing its coordinator or commands, following its test-first process, or deciding which verification steps are required.
Why use it?
They define the checks contributions must pass and prevent the workflow engine from being casually changed. They also make each coding task follow a repeatable testing and review process.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

This is 7xuanlu/ultrapowers's own configuration. It tells Codex and OpenCode how to work on ultrapowers itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ultrapowers configures →

Reuse

Borrowing it

Nothing to install: this file belongs to 7xuanlu/ultrapowers. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/7xuanlu/ultrapowers/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/7xuanlu/ultrapowers

Made for: Codex, OpenCode.

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 ultrapowers AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/7xuanlu/ultrapowers/agents-md/github.svg)](https://agentmods.dev/instructions/7xuanlu/ultrapowers/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/7xuanlu/ultrapowers/agents-md"><img src="https://agentmods.dev/badge/instructions/7xuanlu/ultrapowers/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ultrapowers AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/7xuanlu/ultrapowers/agents-md"><img src="https://agentmods.dev/badge/instructions/7xuanlu/ultrapowers/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,620 This file is loaded in full into every session.
When invoked 1,620 The same file — it is already loaded in full.
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.01620 $0.01620
Opus 5.5 $0.00648 $0.00648
Sonnet 5.5 $0.00324 $0.00324
Haiku 4.5 $0.00162 $0.00162

Measured 1mo ago against content hash 62cc6279889d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ultrapowers 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 1mo 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.

AGENTS.md · 100 lines

How it starts

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

AGENT.md, operating manual for agents working on ultrapowers

Shared, tool-agnostic guidance for any coding agent (Claude Code, Codex, Gemini CLI, …) that contributes to this repo. Claude Code imports it via CLAUDE.md. It is about building ultrapowers itself, not about running the harness on a downstream project.

What this repo is

ultrapowers is a Claude Code Workflow, a deterministic JavaScript coordinator (workflow/ultrapowers-development.js) that hosts Superpowers' SDD/TDD discipline on disposable subagents: plan → per-task (implement under strict TDD → deterministic gate → re-witness-RED → two-stage fail-closed review → fix-loop) → dry-until-clean critic → final integration review. The coordinator makes zero LLM calls; all work tokens are paid by subagents. The /workflows-driven-development command owns the two human gates and dispatches the engine, it must never re-implement the loop.

The discipline bar (eat our own dog food)

This is a tool that gates other people's code on TDD and adversarial review. Contributions are held to the same bar.

  • TDD where it applies, code/logic changes follow red → green → refactor. Write the failing test first, watch it fail, make it pass. Docs, JSON manifests, and CI YAML have no unit test; verify them by validity (parses / lints) and by reading, not by skipping verification.
  • re-witness-RED is the headline mechanism, strip a task's production files, re-run the suite, confirm it fails without them. Never weaken it. Its proof lives in tests/re-witness-red/.
  • Surgical changes, touch only what the task needs; match existing style; no "while I'm here" refactors. No speculative surface (no flags/abstractions/error-handling beyond what's asked).
  • Verify before claiming done, run npm run check; for engine behavior, run the re-witness self-test. Evidence before assertions.

Verification commands

command what it does cost
npm run check parses the engine the way the runtime loads it (strips export, compiles as async IIFE) free, no deps
npm run test:rewitness replays the re-witness-RED catch path through Claude Code spends tokens / needs auth

Read the full file on GitHub · 100 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. 1mo ago First seen · 100 lines · 1,620 tokens per session scan A 62cc6279889d

Subscribe to this mod's changes

ultrapowers AGENTS.md is an instructions file published in the GitHub repository 7xuanlu/ultrapowers (10 stars, last pushed 3mo ago), licensed MIT. It adds 1,620 tokens to every session, about $0.0065 per session on Opus 5.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-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens