ProfFroggo/froggo-mission-control

Mission Control — a self-hosted AI agent platform for Claude Code. Multi-agent orchestration, task management, Gmail, Google Calendar, Kanban, and more.

This repository also configures its own agents. See what froggo-mission-control tells them →

2Stars on the repository
87Mods indexed here, across every type
6mo agoLast push, which is what freshness is scored on
Apache-2.0Licence, which decides whether bodies are shown

senior-coder

25

ProfFroggo/froggo-mission-control

Agent Claude Code

Lead software engineer and architect. Complex multi-file implementations, architecture decisions, hard bugs, systems design. Mentors coder. Use when: task is complex (4+ hours), touches core architecture, requires deep system understanding, or coder needs guidance.

not rated 2 6mo ago A 54 tokens original Apache-2.0

social-manager

26

ProfFroggo/froggo-mission-control

Agent Claude Code

Social media and brand manager. Manages X/Twitter, content calendar, community engagement, and brand voice. Use for: writing tweets, social content strategy, scheduling posts, community replies, influencer coordination, and brand consistency reviews.

not rated 2 6mo ago A 49 tokens original Apache-2.0

voice

27

ProfFroggo/froggo-mission-control

Agent Claude Code

Voice and audio processing agent. Handles transcription, voice command processing, audio session facilitation. Use for: transcribing voice calls, processing audio input, facilitating voice-based sessions, and audio workflow management.

not rated 2 6mo ago A 42 tokens original Apache-2.0

writer

28

ProfFroggo/froggo-mission-control

Agent Claude Code

Content and documentation writer. Writes docs, copy, reports, blog posts, changelogs, and structured content. Use for: documentation, README files, blog posts, marketing copy, user-facing content, technical writing, release notes, and any long-form writing.

not rated 2 6mo ago A 55 tokens original Apache-2.0

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: