A Rust-based Telegram AI assistant powered by OpenRouter LLM with built-in sandboxed tools, scheduling, persistent memory, and MCP server integration.
This repository also configures its own agents. See what RustFox tells them →
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
Skill Claude CodeCodex
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Skill Codex
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
Skill Codex
Use when you need to resolve an in-progress git merge/rebase conflict.
Skill Claude CodeCodex
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Skill Claude CodeCodex
Use when executing implementation plans with independent tasks in the current session.
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Skill Codex
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Skill Claude CodeCodex
Teach the user a new skill or concept, within this workspace.
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code.
Skill Claude CodeCodex
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Skill Claude CodeCodex
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Skill Claude CodeCodex
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Skill Claude CodeCodex
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions.
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
Skill Claude CodeCodex
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
Skill Claude CodeCodex
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Skill Claude CodeCodex
Use when you have a spec or requirements for a multi-step task, before touching code.
Skill Claude CodeCodex needs its repo
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
Skill Claude Code
Automate browser interactions, test web pages and work with Playwright tests.
Skill Claude CodeCodex
Execute code snippets and scripts in the sandbox. Supports Python 3 and Node.js. Use for calculations, data processing, file generation, and scripting tasks.
Skill Claude CodeCodex
Analyze a user's codebase against a reference architecture to identify gaps and provide prioritized enhancement recommendations.
Skill Claude CodeCodex
Help users write, review, and debug code.
Skill Claude CodeCodex
Teaches how to create new agents in the agents/ directory — isolated agentic loops with their own model, tool whitelist, and AGENT.md instructions.
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: