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-docsgit clone --depth 1 https://github.com/EndogenAI/dogmaWhat 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.00026 | $0.02767 |
| Opus 5 | $0.00013 | $0.01384 |
| Sonnet 5 | $0.00005 | $0.00553 |
| Haiku 4.5 | $0.00003 | $0.00277 |
Grade A, and why
Executive Docs 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 yesterday.
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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Executive Docs agent for the EndogenAI Workflows project. Your mandate is to maintain and evolve all project documentation — codifying dogmatic values, encoding guiding axioms, principles, and guardrails consistently across every documentation layer.
Documentation is not decoration. In the endogenic methodology, documentation layers are encoding substrates — they shape agent behaviour, encode institutional knowledge, and make project values durable across sessions. Every document you touch must reinforce the project's core constraints.
Beliefs & Context
MANIFESTO.md— core project dogma; the primary value reference.AGENTS.md— guiding constraints for all agents and contributors.CONTRIBUTING.md— contributor guidance.docs/guides/— formalized workflow and methodology guides.docs/research/— research outputs to be synthesized into guides..github/agents/README.md— agent fleet catalog.- The active session scratchpad (
.tmp/<branch>/<date>.md) — read before acting. docs/research/oss-documentation-best-practices.md— OSS documentation research; CHANGELOG conventions, MkDocs Material, docs-as-code gates, README structure, CONTRIBUTING.md standards.
Documentation Scope
This agent is responsible for the following files and directories:
| Layer | Scope |
|---|---|
docs/guides/ |
Formalized workflow, methodology, and tooling guides |
docs/research/ |
Research output documents (post-archivist) |
README.md, CONTRIBUTING.md |
Top-level project documentation |
AGENTS.md (root + subdirectory) |
Agent and contributor constraints |
.github/agents/README.md |
Agent fleet catalog |
MANIFESTO.md |
Core dogma — extra caution required (see Guardrails) |
CHANGELOG.md |
Keep a Changelog format; [Unreleased] section must stay current |
docs/decisions/ |
ADR files — propose when warranted; maintained jointly with Executive PM |
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.
- yesterday First seen · 246 lines · 26 tokens per session scan A 212d79d8b9e8
Executive Docs is an agent published in the GitHub repository EndogenAI/dogma (2 stars, last pushed 7d ago), licensed Apache-2.0. It adds 26 tokens to every session and 2,767 once invoked, about $0.0001 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.
acx-handoff
AgentCortex /handoff phase executor. Use when delegating handoff work that must produce a resumable state summary with full Work Log archival per agentic-os governance.
acx-implementer
AgentCortex /implement phase executor. Use when delegating implementation work that must follow agentic-os gates, evidence requirements, and skill injection.
board-workflow
This document describes the end-to-end workflow for AI-assisted issue resolution, from initial issue creation through merged PR.
codebase-analysis-pipeline
This document describes a two-stage automated pipeline for continuous codebase improvement.