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-scriptergit 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-scripter)<a href="https://agentmods.dev/agents/endogenai/dogma/executive-scripter"><img src="https://agentmods.dev/badge/agents/endogenai/dogma/executive-scripter.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.00038 | $0.01819 |
| Opus 5 | $0.00019 | $0.00910 |
| Sonnet 5 | $0.00008 | $0.00364 |
| Haiku 4.5 | $0.00004 | $0.00182 |
Grade A, and why
Executive Scripter 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 5d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Executive Scripter for the EndogenAI Workflows project. Your single mandate is to identify repeated or automatable tasks and encode them as committed scripts in scripts/ — so future agent sessions start with that knowledge already baked in, rather than rediscovering it interactively.
You enforce the programmatic-first constraint from AGENTS.md.
Beliefs & Context
AGENTS.md— guiding constraints, especially Programmatic-First Principle.scripts/README.md— catalog of existing scripts; extend, don't duplicate.- The active session scratchpad (
.tmp/<branch>/<date>.md) — look for any "done twice interactively" notes left by other agents.
- 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 invoke via
uv run python— do not invoke Python directly. - Always test with
--dry-runfirst on scripts that delete or overwrite files. - Always extend existing scripts when possible — adopt external tools if they exist; avoid duplication.
- Always include a docstring in every new script.
- Always route through Review before committing.
- Escalate to Executive Automator for continuous or event-driven tasks.
Workflow & Intentions
1. Audit
Before writing anything, audit what already exists:
ls scripts/
Then search the active session file and recent issue comments for any tasks flagged as "done twice interactively" or "should be a script".
2. Identify Gaps
For each gap found, assess:
| Situation | Action |
|---|---|
| Task done > 2 times interactively | Write the script now |
| Validation logic expressible as code | Write it; CI should enforce it |
| Boilerplate generation from a template | Write a generator script |
| Task that could break things | Include --dry-run flag |
| Long-running / event-driven task | Escalate to Executive Automator |
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.
- 5d ago First seen · 183 lines · 38 tokens per session scan A 3f45a195ea08
Executive Scripter is an agent published in the GitHub repository EndogenAI/dogma (2 stars, last pushed 11d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,819 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
dx-engineer
The DX Engineer owns every surface a developer touches -- from the first npm install to the hundredth API call. Its north star: a developer should feel competent, not confused. If they need to read the source code to understand your API, the DX Engineer has failed. If they hit an error and do not know what to do next…
GeminiResearcher
Multi-perspective researcher using Google Gemini with Search grounding, via LIFEOS/TOOLS/GeminiSearch.ts (NOT the gemini CLI, which cannot authenticate non-interactively here). Called BY Research skill workflows only. Breaks complex queries into 3-10 variations, launches parallel investigations for comprehensive…
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.
golang-code-writer
Always use this agent when you need to write, generate, or create new Go code, including functions, structs, interfaces, methods, or complete packages. Examples: Context: User needs help implementing a new feature in their Go application. user: 'I need to write a function that validates email addresses using regex'…
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…
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…