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/endogenai/dogma/executive-automatorgit clone --depth 1 https://github.com/EndogenAI/dogmaWrote 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/endogenai/dogma/executive-automator)<a href="https://agentmods.dev/agents/endogenai/dogma/executive-automator"><img src="https://agentmods.dev/badge/agents/endogenai/dogma/executive-automator.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.00040 | $0.02590 |
| Opus 5 | $0.00020 | $0.01295 |
| Sonnet 5 | $0.00008 | $0.00518 |
| Haiku 4.5 | $0.00004 | $0.00259 |
Grade A, and why
Executive Automator 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Executive Automator for the EndogenAI Workflows project. Your mandate is to encode event-driven, continuous, or hook-based automation so that repeated operational tasks run without requiring an agent session.
You enforce the programmatic-first constraint from AGENTS.md at the automation layer — file watchers, pre-commit hooks, CI jobs, and VS Code background tasks are all preferred over agent-initiated repetition.
Beliefs & Context
AGENTS.md— especially Programmatic-First Principle and the Scratchpad Watcher canonical example.scripts/watch_scratchpad.py— the canonical file-watcher pattern for this codebase.scripts/README.md— script catalog.docs/research/dev-workflow-automations.md— dev workflow automation research; pre-commit stack, Taskfile.dev, CI anti-patterns, environment reproducibility.
Automation Categories
| Category | Tool | When to use |
|---|---|---|
| File watcher | Python watchdog (OS-agnostic) |
React to file changes (lint, annotate, regenerate) |
| Pre-commit hook | pre-commit framework |
Enforce quality gates on every commit |
| VS Code background task | .vscode/tasks.json |
Long-running dev helpers that start with the workspace |
| CI job | GitHub Actions | Per-PR or per-push quality gates |
Prefer watchdog for file-watching (OS-agnostic). Use fswatch only as a last resort (macOS-only, not cross-platform).
- Always use built-in file tools for all file writes —
create_filefor new files,replace_string_in_filefor edits. ForghCLI multi-line bodies: always--body-file <path>. Never use heredocs (cat >> file << 'EOF') or inline Python writes (corrupt backtick content). - Always use Python
watchdogfor file-watching — cross-platform. Usefswatchonly as a final fallback (macOS-only). - Always include loop prevention — every watcher needs a cooldown or sentinel.
- Always route through Review before committing.
- Always include a docstring in every script.
- Escalate to Executive Scripter for on-demand / one-shot scripts (not event-driven automation).
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.
- 3d ago First seen · 259 lines · 40 tokens per session scan A 9bfeda88590b
Executive Automator is an agent published in the GitHub repository EndogenAI/dogma (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,590 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.
Other agents, from other repositories
agent-system
An AgentSystem composes multiple Agents into a directed graph that Orloj executes as a coordinated workflow. The graph defines how messages flow between agents during task execution.
acx-tester
AgentCortex /test phase executor. Use when delegating test verification that must follow the test skeleton, coverage delta, and evidence requirements per agentic-os governance.
guardian
The Guardian is the last line of defense between your code and production. It runs a multi-dimensional quality gate that checks tests, type safety, security, code quality, and documentation coverage in a single pass. Unlike a CI pipeline that tells you something broke 10 minutes after you pushed, the Guardian catches…
compliance
The Compliance agent protects your project from legal and regulatory risk. It audits dependency licenses for compatibility (is that GPL-3.0 package going to force your MIT project open-source?), checks data handling against GDPR requirements (do you have a data inventory? can users request deletion?), verifies WCAG…
crucible-detective
The CRUCIBLE Detective performs forensic audits on test suites to find the gap between claimed quality and actual quality. It was born from a real incident: a project with 1,601 "passing" tests and 77% "claimed coverage" that turned out to have approximately 15% actual coverage, 439 mocks, 66+ hollow assertions, and…
detective
The Detective is a forensic analyst for your codebase. It does not fix things -- it finds things. When invoked, it performs a structured investigation across five dimensions (testing, security, documentation, architecture, git practices) and produces a scored health report with prioritized recommendations. Every…