Borrowing it
Nothing to install: this file belongs to hekivo/superpowers-sage. 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/hekivo/superpowers-sage/main/AGENTS.mdgit clone --depth 1 https://github.com/hekivo/superpowers-sageWrote 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/hekivo/superpowers-sage/agents-md)<a href="https://agentmods.dev/instructions/hekivo/superpowers-sage/agents-md"><img src="https://agentmods.dev/badge/instructions/hekivo/superpowers-sage/agents-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.01030 | $0.01030 |
| Opus 5 | $0.00515 | $0.00515 |
| Sonnet 5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
superpowers-sage 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- superpowers-sage CLAUDE.md — 97% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Superpowers Sage — Universal Rules
Rules applied in every session where this plugin is active. These take precedence over skill-local guidance unless a skill explicitly overrides.
Environment
- All
wp,composer,artisan,yarn,npmcommands run vialando <cmd>. Never invoke these binaries directly on the host. - Sage projects use Bedrock. Custom code lives in
web/app/, never inweb/wp/. - The plugin supports Claude Code, VS Code Copilot, Cursor, and OpenAI Codex.
When contributing to this plugin — adding or updating automation hooks —
keep
hooks/hooks.jsonandhooks/cursor-hooks.jsonin sync viascripts/sync-cursor-hooks.mjs. Manifest versions across.claude-plugin/,.cursor-plugin/, and.codex-plugin/are aligned byscripts/sync-codex-manifests.mjs(also enforced in CI). The Codex CLI (>= 0.137) layout —.agents/plugins/marketplace.json, the real-content plugin underplugins/superpowers-sage/, andAGENTS.md(these universal rules, mirrored for Codex/AGENTS-aware tools) — is generated from the root source (skills/,hooks/,.codex-plugin/plugin.json, and thisCLAUDE.md) byscripts/build-codex-plugin.mjs; run it after changing those, never edit the generated files (AGENTS.md,plugins/,.agents/) by hand (CI enforces sync via--check). Codex does not load a plugin'sCLAUDE.md; it readsAGENTS.mdfrom the project root — see README → OpenAI Codex.
Protected files (never edit directly)
.env,wp-config.php— managed by Bedrock/Trellis Vault. Suggestansible-vault editor Bedrock.envpattern instead.bedrock/config/environments/*.php— environment-specific config.trellis/group_vars/*/vault.yml— secrets.
If Claude needs to modify these, it MUST ask the user first with a concrete alternative path.
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.
- 7d ago First seen · 84 lines · 1,030 tokens per session scan A 9f82b9181919
superpowers-sage AGENTS.md is an instructions file published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 2mo ago), licensed MIT. It adds 1,030 tokens to every session, about $0.0052 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
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.
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).
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).
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.
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.