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.
curl -O https://raw.githubusercontent.com/7xuanlu/ultrapowers/main/CLAUDE.mdgit clone --depth 1 https://github.com/7xuanlu/ultrapowersWrote 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.
[](https://agentmods.dev/instructions/7xuanlu/ultrapowers/claude-md)<a href="https://agentmods.dev/instructions/7xuanlu/ultrapowers/claude-md"><img src="https://agentmods.dev/badge/instructions/7xuanlu/ultrapowers/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00512 | $0.00512 |
| Opus 5 | $0.00256 | $0.00256 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
ultrapowers CLAUDE.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 8d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@AGENTS.md
CLAUDE.md, Claude Code specifics for ultrapowers (shared principles are in AGENTS.md above)
Workflow
This repo's own development uses Superpowers skills (this is the dog-food): brainstorming →
writing-plans → subagent-driven execution under strict TDD → requesting-code-review →
finishing-a-development-branch. Worktree per feature (feature/<kebab>), PR before merge, never
push to main directly. The skills own TDD, worktree, and model-routing rules, don't restate them.
The engine and command are the product, treat them as such
workflow/ultrapowers-development.jsis the deterministic coordinator. It is loaded by the Workflow tool with top-levelawait/returnand a singleexport, that's whynpm run checkcompiles it as an async IIFE instead ofnode --check. Don't add a secondexportshape without updatingtests/check-engine.sh.skills/workflows-driven-development/SKILL.mdis user-only (disable-model-invocation: true) and spends real tokens. It dispatches the engine byscriptPath(the engine is not registered by name in~/.claude/workflows/, so it stays out of the slash list and the model can't dispatch it directly, bypassing the gates); do not re-implement the loop inside the skill. (Ships as askills/skill, not acommands/file, so the slash picker shows the short nameworkflows-driven-development (ultrapowers)instead of the full/ultrapowers:workflows-driven-developmentpath.)
After any edit
Run npm run check. For engine-behavior changes, run npm run test:rewitness (spends tokens) and
confirm the vacuous test is CAUGHT and the good test passes. Don't claim an engine change works
without one of these.
Distribution
The repo is a self-contained plugin marketplace: .claude-plugin/plugin.json +
.claude-plugin/marketplace.json (source: "./"). It is also listed in the author's aggregator
marketplace (7xuanlu/claude-plugins). Keep version in sync across plugin.json,
marketplace.json, and package.json when you cut a release; tag it.
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.
- 8d ago First seen · 37 lines · 512 tokens per session scan A 866c0294c9fb
ultrapowers CLAUDE.md is an instructions file published in the GitHub repository 7xuanlu/ultrapowers (10 stars, last pushed 2mo ago), licensed MIT. It adds 512 tokens to every session, about $0.0026 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
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.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.