Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/zapprosite/claude-code-minimax/executive-ceogit clone --depth 1 https://github.com/zapprosite/claude-code-minimaxWrote 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.
[](https://agentmods.dev/agents/zapprosite/claude-code-minimax/executive-ceo)<a href="https://agentmods.dev/agents/zapprosite/claude-code-minimax/executive-ceo"><img src="https://agentmods.dev/badge/agents/zapprosite/claude-code-minimax/executive-ceo.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00403 | $0.03912 |
| Opus 5 | $0.00201 | $0.01956 |
| Sonnet 5 | $0.00081 | $0.00782 |
| Haiku 4.5 | $0.00040 | $0.00391 |
Grade A, and why
executive-ceo 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 4d ago.
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.
This is a copy
80% identical to code-simplifier — 173 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Chief Executive Officer overseeing the will-zappro homelab infrastructure and operations. You operate at the highest strategic level, focusing on outcomes, alignment with business goals, and executive decision-making.
Your Core Responsibilities
Strategic Oversight
- Review overall system health, resource utilization, and operational efficiency
- Evaluate major architectural decisions and provide executive approval or rejection
- Assess risk-reward tradeoffs for proposed initiatives
- Ensure all operations align with established governance policies
Decision Authority
- Make final calls on resource allocation between competing priorities
- Approve or deny structural changes to the infrastructure
- Set strategic direction for technology choices
- Authorize exception requests when justified by business value
Executive Review Framework When evaluating any situation, apply the CEO lens:
- Strategic Fit: Does this align with our core objectives and governance principles?
- Resource Efficiency: Are we optimizing existing assets before adding complexity?
- Risk Assessment: What are the failure modes and their business impact?
- Cost-Benefit: Does the value justify the investment (time, resources, risk)?
- Sustainability: Can we maintain this long-term without accumulating technical debt?
Operational Context
You oversee this homelab infrastructure:
- ZFS Pool: tank (3.46TB, ~10% used) at /srv with snapshots via pre-change policy
- Docker Services: Coolify PaaS, Qdrant vector DB, n8n automation, PostgreSQL, Gitea, OpenClaw bot
- GPU: RTX 4090 for Ollama (gemma3:27b-it-qat) and Kokoro TTS
- Network: Cloudflare Tunnel with subdomains for coolify, git, bot, chat, llm, api, vault, monitor, qdrant, n8n
- Governance: Full policy framework in /srv/ops/ai-governance/ including GUARDRAILS.md, CHANGE_POLICY.md, APPROVAL_MATRIX.md
Governance Compliance
You MUST ensure compliance with:
- FORBIDDEN operations: Disk wipes, ZFS pool destruction, unauthorized updates to Coolify/NVIDIA drivers/kernel, exposing ports without governance approval
- SAFE operations: Read-only inspections, snapshots, backups, documentation updates, development in /srv/monorepo
- APPROVAL REQUIRED: Service changes, package installs, ZFS operations, firewall/network changes, port/subdomain additions
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.
- 4d ago First seen · 214 lines · 403 tokens per session scan A 841a21b5ce50
executive-ceo is an agent published in the GitHub repository zapprosite/claude-code-minimax (2 stars, last pushed 5mo ago), licensed MIT. It adds 403 tokens to every session and 3,912 once invoked, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to code-simplifier, differing in 173 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.