Invariant-driven Firefox investigation for Codex. Use for suspicious code, possible security issues, suspected specification violations, or vague claims that need static validation, reachability analysis, proof tests, and a revision-pinned bug-style report.
Independent red-team review for Firefox root-cause analyses and proposed fixes. Use to critique an analysis, patch, Phabricator revision, commit, diff, or working tree with isolated Codex subagents and structured verdicts.
First-principles Firefox problem solving for Codex. Use for Bugzilla bugs or Firefox failures that need evidence-based diagnosis, revision-pinned source links, proof tests, invariant-driven solution design, independent evaluation, implementation, and durable…
Hypothesis-driven Firefox investigation: given a freeform suspicion that some code is buggy, unsafe, mis-behaving, or non-spec, blindspot validates the claim, finds real user-facing or security consequences (or proves there are none), and writes a bug-style…
RedPen — independent review of a proposed root-cause-analysis solution. Spawns an isolated reviewer with no shared memory; returns a structured review doc with verdict, alternatives, and concerns. Reusable from any RCA/bugfix skill (sherlock, fuzzbug-fix,…
First-principles problem solving for Firefox bugs. Evidence-based root cause analysis with permanent source links and proof tests, then invariant-driven solution design, independent evaluation, implementation, and documentation.
Prepare, reproduce, and audit standalone upstream security reports for third-party media libraries Firefox vendors, including FFmpeg/ffvpx, libvpx, libaom, dav1d, the Xiph libraries, libpng, libjpeg-turbo, libsoundtouch, libsrtp, libwebrtc, libyuv, libwebp,…
Prepare, reproduce, and audit standalone upstream security reports for the third-party media libraries Firefox vendors — FFmpeg/ffvpx, libvpx, libaom, dav1d, the Xiph libraries, libpng, libjpeg-turbo, libsoundtouch, libsrtp, libwebrtc, libyuv, libwebp,…