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 skills add strigov/superpowers-strigov-ver --skill codex-askgit clone --depth 1 https://github.com/strigov/superpowers-strigov-verWrote 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/skills/strigov/superpowers-strigov-ver/codex-ask)<a href="https://agentmods.dev/skills/strigov/superpowers-strigov-ver/codex-ask"><img src="https://agentmods.dev/badge/skills/strigov/superpowers-strigov-ver/codex-ask.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.00091 | $0.01194 |
| Opus 5 | $0.00046 | $0.00597 |
| Sonnet 5 | $0.00018 | $0.00239 |
| Haiku 4.5 | $0.00009 | $0.00119 |
Grade A, and why
codex-ask 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Ask (advisory second opinion)
Free-form second opinion from Codex on any matter — architecture decisions, debugging hypotheses, research conclusions, trade-off calls — not just plans and diffs. Codex answers from inside the repository (read-only), so its opinion is grounded in the actual code, not in whatever excerpt happened to be quoted. Ported from TRIP-workflow's codex-ask onto the codex-dispatch runtime.
Advisory, not authoritative. Unlike the dev-orchestrator review loops, there are no verdict tokens and nothing is gated on the answer: treat the response as one input to your judgment, exactly like a colleague's opinion. Agreement is weak evidence; disagreement is a strong signal — when Codex disagrees with your draft position, surface its answer to the user verbatim; the disagreement itself is the valuable output.
When to use
- Second opinion on an architecture/design decision before it hardens (end of a research/brainstorm session, before writing a plan).
- Root-cause help when genuinely stuck on a bug — different model family, different blind spots.
- "Red-team this conclusion" on a memo or recommendation you are about to present.
When NOT to use
- Questions that need the user's preference or judgment — ask the user, not Codex.
- Trivial lookups or anything settled by reading the code yourself — every ask costs a Codex run.
- As a gate: never block or approve work based on the answer. That is what dev-orchestrator's review loops with verdict tokens are for.
- From the dev-orchestrator main thread while its protocol is active — the orchestrator's channels are fixed (Opus judgment, Explore research); an unscheduled Codex opinion is protocol drift.
Invocation
Codex is invoked via codex-dispatch — read the codex-invocation skill first (wrapper resolution, --background, Monitor polling, result fetch).
Topic state
One discussion = one topic = one Codex thread. Persist the mapping in the repo's git dir so follow-ups survive session restarts without polluting the working tree:
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 · 96 lines · 91 tokens per session scan A e71a5f20111b
codex-ask is a skill published in the GitHub repository strigov/superpowers-strigov-ver (4 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 1,194 once invoked, about $0.0005 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.