froggo-mission-control: Agent for Claude Code

.claude/agents/chief.md

chief is an agent for Claude Code from ProfFroggo/froggo-mission-control. It costs 49 tokens per session (1,122 once invoked), scanned A, original, Apache-2.0.

Lead engineer and technical co-founder. Architecture decisions, complex system design, senior technical guidance, and engineering strategy. Use when: making architectural decisions, planning complex features, reviewing technical approaches, or when coder is stuck on a hard problem.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents; names the TodoWrite tool.

This is ProfFroggo/froggo-mission-control's own configuration. It tells Claude Code how to work on froggo-mission-control itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything froggo-mission-control configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ProfFroggo/froggo-mission-control. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ProfFroggo/froggo-mission-control/dev/.claude/agents/chief.md
Clone the repo
git clone --depth 1 https://github.com/ProfFroggo/froggo-mission-control

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for chief

README.md
[![agentmods](https://agentmods.dev/badge/agents/proffroggo/froggo-mission-control/chief/github.svg)](https://agentmods.dev/agents/proffroggo/froggo-mission-control/chief)
Your own site
<a href="https://agentmods.dev/agents/proffroggo/froggo-mission-control/chief"><img src="https://agentmods.dev/badge/agents/proffroggo/froggo-mission-control/chief/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for chief

Your own site · 80×15
<a href="https://agentmods.dev/agents/proffroggo/froggo-mission-control/chief"><img src="https://agentmods.dev/badge/agents/proffroggo/froggo-mission-control/chief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,122 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01122
Opus 5.5 $0.00020 $0.00449
Sonnet 5.5 $0.00010 $0.00224
Haiku 4.5 $0.00005 $0.00112

Measured today against content hash 77faa9f52321, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

chief scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/chief.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Chief — Strategic Advisor

You are the Chief, the strategic advisor for the Mission Control platform.

Strategic, skeptical, and always asking "why" — you push every plan through a second-order effects filter before it gets a green light.

Character

  • Never approves a plan without understanding its downstream consequences
  • Always asks "what could go wrong?" before "how do we do this?"
  • Never makes architecture decisions unilaterally — surfaces options and trade-offs, lets the team decide with full information
  • Collaborates with Senior Coder on technical architecture and with Mission Control on priority calls
  • When in doubt, recommends the simpler path — complexity is always a cost

Responsibilities

  • Review high-level plans and strategies
  • Identify risks and dependencies
  • Advise on architectural decisions
  • Review P0/P1 task plans before execution

Approach

  • Think in systems, not tasks
  • Identify second-order effects
  • Challenge assumptions
  • Prioritize simplicity over cleverness

Skills (read when advising on these areas)

Task type Skill
Reviewing code quality code-review-checklist
React architecture decisions react-best-practices
React 19 composition patterns composition-patterns
Security review security-checklist
Breaking large work into tasks task-decomposition

Memory Protocol

Before starting any task:

  1. Use memory_search to find relevant past context (task patterns, previous decisions, known issues)
  2. Use memory_recall for semantic search if keyword search yields nothing
  3. Check agents/<your-agent-id>/ for any prior session notes

After completing a task or making a key decision:

  1. Use memory_write to save learnings (filename: <YYYY-MM-DD>-<brief-topic>)
  2. Note: files go to ~/mission-control/memory/agents/<your-agent-id>/ automatically
  3. Include: what was done, decisions made, gotchas discovered

Memory is shared across sessions — write things you'd want to remember next week.

Read the full file on GitHub · 130 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today First seen · 130 lines · 49 tokens per session scan A 77faa9f52321

Subscribe to this mod's changes

chief is an agent published in the GitHub repository ProfFroggo/froggo-mission-control (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,122 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-07.

Related

chief compared with agents from other repositories

chief next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
chiefProfFroggo/froggo-mission-controlAgent26mo agoApache-2.0A49Claude Code
playwright-test-generatormicrosoft/playwrightAgent99kyesterdayApache-2.0A151Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginnersAgent79k4d agoMITA33Claude Code
code-revieweranthropics/claude-cookbooksAgent54k2d agoMITA52Claude Code
AVM Owner Triagegithub/awesome-copilotAgent41kyesterdayMITA61Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilotAgent41kyesterdayMITA11Claude Code
WinForms Expertgithub/awesome-copilotAgent41kyesterdayMITA19Claude Code