An AI-powered workforce platform that executes multi-agent tasks with automatic provider failover and CEO agent orchestration. It detects technology stacks across 1,000+ platforms and provisions industry-specific specialists while running on customer hardware with no data leaving their network.
Build and run a structured agent harness — an outer loop that gives an LLM a defined set of tools (capabilities) and drives it to task completion. Use when: you need an agent that can take multi-step autonomous action on a complex task.
Convert a chaotic list of scattered ideas, notes, or thoughts into a structured, prioritized action plan. Use when: you have a messy list of ideas and need structure.
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
Multi-perspective code review before merging. Simulates a council of reviewers (security, correctness, performance, maintainability) independently evaluating a change. Use before any PR merge or for significant changes.
Audit training data and tokenizer pipelines for quality issues that silently degrade LLM training. Use when: preparing a dataset for LLM pretraining or fine-tuning.
Review, validate, and update Python dependencies safely. Use when adding a new package, upgrading an existing one, or reviewing the dependency surface.
Remove AI code slop before committing. Review AI-generated code for unnecessary verbosity, redundant comments, over-engineering, and low-signal patterns that degrade codebase quality over time.
Clone an existing plan, task thread, or agent session so you can explore an alternative approach without losing the original. Use when: you want to try a risky refactor without throwing away the current plan.
Implement new features behind feature flags to enable safe, gradual rollouts and easy rollbacks without code deployments. Use when: implementing a risky or large feature.
Ensures the repository's git history, branch state, and commit messages are clean, meaningful, and follow project conventions before pushing or merging. Use before pushing commits to master or opening a PR.
Converts this codebase into a queryable knowledge graph so AI sessions query graph.json (71.5x fewer tokens) instead of reading raw source files. Integrates with Claude Code and Codex via repo hooks that auto-refresh on session start and after turns.
Plan a multi-file or multi-step implementation before writing any code. Use before any change touching more than two files, adding a new feature, or changing a module interface.
Analytics, heatmaps, and trends from session history. Analyze checkpoint logs, learnings, and git history to surface patterns: which files change most, which steps fail most often, and where to invest in tooling or tests.
Provides a structured, repeatable process for resolving GitHub issues from start to finish — reading the issue, planning a solution, implementing it, testing it, and closing it with a proper commit and changelog entry. Use when assigned a GitHub issue to implement or fix.
Persist corrections and patterns to long-term memory. When a mistake is made or a rule is learned, write it to .claude/state/learnings.md so it's never repeated.
Route prompts to a locally running Ollama instance instead of cloud AI APIs. Use when: processing sensitive/proprietary code or data that shouldn't leave the machine.
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: