Specialized sub-agent for the AI co-mathematician system. Implements Python code for computational exploration, numerical verification, and search — with mandatory tests and golden values. Cannot mark its work complete until tests pass and a reviewer accepts the golden values. Use when the project-coordinator…
Specialized sub-agent for the AI co-mathematician system. Attempts to formalise a stated lemma in Lean 4 and verify it with lake build. A successful Lean build is the strongest form of "proven" the system supports — accepted by paper-reviewer with only plumbing checks, not mathematical re-checking. Use when the…
Specialized sub-agent for the AI co-mathematician system. Performs literature searches and produces verified, cited workstream reports for a math research project. Use when the project-coordinator dispatches a literature workstream, when a workstream needs to confirm prior art, or when a claim in paper.tex needs…
Adversarial reviewer agent for the AI co-mathematician system. Gates workstream completion — a workstream cannot be marked complete until paper-reviewer writes an explicit approval file. Cross-checks references resolve, that proofs have no leftover \unproven blocks (or are properly flagged), that code outputs match…
The front door of an AI co-mathematician research project. Reads goals.md, talks to the user as a sounding board, formalizes research intent, dispatches workstreams to specialized sub-agents (literature-reviewer, prover, coder), and uses progressive disclosure to filter low-level chatter from the user. Use when the…
Specialized sub-agent for the AI co-mathematician system. Drafts mathematical proofs into paper.tex with strict discipline — every step is justified, cited, or explicitly marked \unproven. Never hand-waves. Use when the project-coordinator dispatches a proof workstream, or when a specific lemma/theorem in the paper…
Initialize a disciplined AI co-mathematician research project for Codex. Use when starting a math or economic theory investigation that needs goals.md, paper.tex, workstreams, decisions, reviewer approvals, strict no-hand-waving proof tracking, Lean/code workstreams, or a durable co-math project scaffold.
Render a compact status view for a Codex co-mathematician project. Use when the user asks for project status, active workstreams, blocked items, pending reviews, open proof obligations, recent decisions, or "what is happening in this co-math project".
Run an adversarial mathematical workflow in Codex: verify proofs, write hard proofs, explore conjectures, search for counterexamples, and triage possible gaps. Use for important theorem checks, failed proof attempts, conjectures, independent verification, or requests like 'audit this proof', 'find a counterexample'…
Write rigorous, gap-free mathematical proofs for academic research. Use when asked to prove, derive, justify analytically, expand a proof sketch, check a theorem statement, or turn economic or game-theoretic reasoning into a complete proof with explicit algebra, signs, edge cases, and no hand-waving.
Polish verified mathematical proofs without changing their mathematical content. Use after a proof has been accepted by the user, a reviewer, Lean, or a co-math review cycle; or when asked to improve proof exposition, readability, signposting, notation, references, or grammar while preserving the original argument.
Set up and use an academic "second brain" — agentic RAG over a local library of theoretical papers (LaTeX-aware ingestion, theorem/proof tools, hybrid search). Use when the user wants a second brain for papers in a folder, says "/second-brain", "set up a second brain here", "ingest this paper into my second brain", or…