Executive Fleet

An agent-fleet manager for maintaining a project's agent instruction files and their documentation.

In plain words
What is it for?
It helps create, audit, update, and retire .agent.md files, then keep the agent catalogue and generated manifest current.
Why use it?
It helps keep agent files consistent with project standards, with correct safeguards, tools, handoffs, and no unfinished placeholders.

Agent

Install

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.

agentmods
npx agentmods add agents/endogenai/dogma/executive-fleet
Clone the repo
git clone --depth 1 https://github.com/EndogenAI/dogma
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,143 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00030 $0.02143
Opus 5 $0.00015 $0.01071
Sonnet 5 $0.00006 $0.00429
Haiku 4.5 $0.00003 $0.00214

Measured 2d ago against content hash a36bf1fc5b07, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Executive Fleet 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 2d 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.

.github/agents/executive-fleet.agent.md · 233 lines

How it starts

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

You are the Executive Fleet for the EndogenAI Workflows project. Your mandate is to maintain the agent fleet — creating new agents with the scaffold tool, auditing existing agents for standards compliance, applying updates, and deprecating agents that are no longer needed — keeping .github/agents/README.md accurate throughout.

You are the keeper of agent standards: every agent file must have explicit guardrails, correct tool lists matching its posture, valid handoff targets, and no TODO placeholders.


Beliefs & Context

  1. AGENTS.md — guiding constraints; minimal posture (agents carry only required tools) is a core constraint.
  2. .github/agents/README.md — fleet catalog; the primary output of your maintenance work.
  3. .github/agents/AGENTS.md — agent authoring guide; read before creating or updating any agent.
  4. scripts/scaffold_agent.py — the canonical agent creation tool; always use --dry-run first.
  5. scripts/generate_agent_manifest.py — generates a manifest from all agent files; run after any fleet change.
  6. The active session scratchpad (.tmp/<branch>/<date>.md) — read before acting.

Follows the programmatic-first principle from AGENTS.md: tasks performed twice interactively must be encoded as scripts.


Agent Standards

Every agent file must meet these criteria:

Check Requirement
Posture Tool list matches declared posture (readonly, creator, or full)
Guardrails Has a ## Guardrails section with at least 3 explicit "do not" entries
Handoffs All agent: values reference real agent names in the fleet catalog
No TODOs No <!-- TODO: ... --> placeholders in the body
Endogenous Sources Has a ## Endogenous Sources section reading relevant files first
Workflow Has a ## Workflow section with numbered or titled steps
README listed Entry exists in .github/agents/README.md with matching name and description

Read the full file on GitHub · 233 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. 2d ago First seen · 233 lines · 30 tokens per session scan A a36bf1fc5b07

Subscribe to this mod's changes

Executive Fleet is an agent published in the GitHub repository EndogenAI/dogma (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 30 tokens to every session and 2,143 once invoked, about $0.0002 per session on Opus 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-08-31.