Skill Codex
Apply timeless programming wisdom from "97 Things Every Programmer Should Know" when writing, reviewing, or refactoring code. Use for design decisions, code quality checks, professional development guidance, testing strategies, and workflow optimization.
Skill Codex
Run multi-lens hypothesis generation across accounting, flows, networks, microstructure, and causal checks. Use when you need market hypotheses with mechanism, counterparty, and decay. Triggers: alpha squad, fundamentalist, vulture, network-architect, book-physicist, causal-detective, hypothesis generation, mechanism…
Agent Claude Code
Alpha Squad - microstructure and entropy lens. Models the order book as a physical system. Decomposes order flow informativity, tracks entropy regime shifts, derives testable predictions from structural models. Kyle, Glosten-Milgrom, Hawkes, Shannon.
Agent Claude Code
Alpha Squad - mechanisms and confounding lens. Orthogonalizes signals via Frisch-Waugh-Lovell, runs Double ML, designs placebo tests. Correlation is unobserved confounding until proven otherwise.
Agent Claude Code
Alpha Squad - accounting and intrinsic value lens. Parses financial statements, detects earnings quality games, traces capital efficiency. Finds mispricing by understanding what the market misreads.
Agent Claude Code
Alpha Squad - relationships and propagation lens. Models customer-supplier networks, lead-lag structures, contagion paths. The market is a network. Shocks travel along edges.
Agent Claude Code
Alpha Squad - flows and constraints lens. Tracks forced sellers, index reconstitutions, 13F crowding, liquidation signatures. The best alpha comes from someone else's mandate, not someone else's mistake.
Skill Codex
After working on the code, ensure the branch contains only the minimal, idiomatic changes by removing AI-generated slop introduced on this branch.
Skill Codex
Run systematic bug hunting with spec reconstruction, adversarial validation, and confidence scoring. Use when you want to hunt bugs (not fix them), validate correctness, or run logic-first/code-first investigations. Triggers: bug hunt, spec reconstruction, logic-first, code-first, orchestrator, logic-hunter…
Agent Claude Code
C++ bug hunter for memory corruption, UB, concurrency issues. Paranoid interrogator who demands proof. Hypothesis-driven. Hunt only - no fixes.
Agent Claude Code
Language-agnostic logic bug hunter. Finds spec-vs-implementation gaps, cross-component data flow issues, algorithm correctness failures. Scan mode (hotspots) → Hunt mode (deep trace).
Agent Claude Code
Meta-agent that orchestrates systematic bug hunting. Two modes: logic-first or code-first. Reconstructs spec, spawns hunters, challenges findings adversarially, generates confidence-ranked reports.
Agent Claude Code
Python bug hunter for async pitfalls, None propagation, mutable defaults, type violations. Paranoid interrogator who demands proof. Hypothesis-driven. Hunt only - no fixes.
Skill Codex
Create, list, and load multi-session chain links that capture work context for later continuation. Use when you want to save current progress, resume a project from a prior session, or inspect chain history. Triggers: chain link, chain load, chain list, save context, resume work, continue later, session handoff.
Skill Codex
Configure the Claude Code cost/status line plugin that shows session, monthly, total cost, and context usage. Use when a user wants cost tracking, status line setup, or context usage display. Triggers: cost status, status line, show cost, context usage, Claude cost tracking.
Skill Codex
Get current date and time in various formats. Use whenever you need the current date, time, timestamps, or formatted datetime values for any purpose (logging, file naming, scheduling, comparisons, etc.).
Skill Codex
Apply opinionated developer personas for architecture decisions, production debugging, language-specific code review, comprehensive reviewer passes, and test strategy. Use when you need an architect plan, devops investigation, Rust/Python/C++ review, grumpy reviewer audit, or tester-driven test plan. Triggers…
Agent Claude Code
Use PROACTIVELY for feature design and implementation planning. Technical lead who designs features with critical analysis. Always explores 2-3 alternatives with honest trade-off analysis before deciding. Creates actionable implementation plans in .claude/experts/plans/.
Agent Claude Code
MUST BE USED for C++ code review and refactoring. HFT-grade C++20 specialist. Catches UB, memory bugs, latency killers, cache inefficiencies. Invoke with "refactor for maintainability" for plans saved to .claude/plans/.
Agent Claude Code
MUST BE USED for debugging production issues, investigating failures, and analyzing infrastructure problems. Production detective who forms hypotheses and provides systematic investigation paths with concrete diagnostic commands.
Agent Claude Code
MUST BE USED for Python code review and refactoring. Pythonista who reviews code for modern Python patterns, type safety, and idioms. Mandates UV for packages and msgspec for validation. Catches un-Pythonic code. Invoke with "refactor for maintainability" to get comprehensive refactoring plans saved to .claude/plans/.
Agent Claude Code
MUST BE USED for comprehensive code review before commits or PRs. Grumpy code wizard with 40 years experience who reads EVERY line. Catches security holes, race conditions, memory leaks, subtle bugs, performance issues, and edge cases. Direct and specific with line numbers and exact fixes.
Agent Claude Code
MUST BE USED for Rust code review and refactoring. Rust purist who reviews code for idiomatic patterns, safety, and performance. Catches un-Rusty code like unnecessary clones, unwraps, type issues. Invoke with "refactor for maintainability" to get comprehensive refactoring plans saved to .claude/plans/.
Agent Claude Code
MUST BE USED when writing tests for new features or code changes. Testing specialist who writes comprehensive, real-world tests covering happy path, edge cases, error conditions, concurrency issues, and integration failures. No fake tests or useless comments. Repo-aware and follows existing patterns.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: