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 rules/mzored/superpowers-cc-to-codex/skillsgit clone --depth 1 https://github.com/mzored/superpowers-cc-to-codexWrote 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/rules/mzored/superpowers-cc-to-codex/skills)<a href="https://agentmods.dev/rules/mzored/superpowers-cc-to-codex/skills"><img src="https://agentmods.dev/badge/rules/mzored/superpowers-cc-to-codex/skills.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.00000 | $0.00236 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
skills 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 6d 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.
What it actually says
Skills
Prompt-driven workflow definitions for forked Superpowers skills.
Structure
Each skill directory contains:
SKILL.md— Orchestration checklist for Claude (the controller)prompts/*.md— Detailed execution guidance sent to Codex agents- Optional templates (
*-template.md) and supporting methodology docs
Conventions
- SKILL.md is for Claude: concise checklists, status handling, decision points
- prompts/ are for Codex: detailed task structure, self-review, escalation protocols
- Every SKILL.md carries an upstream sync header referencing the original Superpowers skill
- Hard gates prevent implementation without approved design (brainstorming skill)
- Systematic debugging enforces root cause investigation before any fix attempt
Anti-Patterns
- Putting detailed execution guidance in SKILL.md instead of prompts/
- Creating skills without a Codex agent, schema, and prompt
- Skipping the design approval gate in brainstorming
- Fixing symptoms without root cause investigation (systematic-debugging)
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.
- 6d ago First seen · 32 lines · 0 tokens per session scan A b39570cbe491
skills is a cursor rule published in the GitHub repository mzored/superpowers-cc-to-codex (7 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 236 tokens. 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 cursor rules, from other repositories
context-delegate
Context Gatherer & External LLM Prompt Generator.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
enterprise-architect
Enterprise System Architect & High-Level Auditor.
controlflow-docs-evals
Rules for documentation parity, localized tutorials, and eval verification.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.