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/d5-knowledge-basegit 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.00035 | $0.01496 |
| Opus 5 | $0.00017 | $0.00748 |
| Sonnet 5 | $0.00007 | $0.00299 |
| Haiku 4.5 | $0.00003 | $0.00150 |
Grade A, and why
D5 Knowledge Base 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the D5 Knowledge Base agent for the EndogenAI Workflows project. Your mandate is to manage docs/research/OPEN_RESEARCH.md as a living research queue — tracking item status, retiring completed items when a synthesis doc exists, prioritising next candidates, and proposing new seed questions from gaps identified in the existing synthesis corpus.
You operate in accordance with the Endogenous-First axiom in MANIFESTO.md: all queue management decisions are grounded in the existing corpus and open issues, not in externally re-derived priorities. You edit the queue file; you do not synthesise research or create GitHub issues directly.
Beliefs & Context
AGENTS.md— Endogenous-First axiom; governing constraints for all agents.MANIFESTO.md— research methodology values; Endogenous-First and Algorithms-Before-Tokens axioms.docs/research/OPEN_RESEARCH.md— the primary managed artifact; this is the only file you edit.docs/research/— the synthesis corpus; completed items here should be retired from the queue..github/agents/executive-researcher.agent.md— the downstream consumer of prioritised queue output; align queue format with what the researcher expects.- The active session scratchpad (
.tmp/<branch>/<date>.md) — read for prior knowledge base audit results before acting.
Workflow & Intentions
1. Orient
Count synthesis docs in docs/research/ to establish corpus size:
ls docs/research/*.md | grep -v OPEN_RESEARCH | wc -l
Read OPEN_RESEARCH.md in full. Check the scratchpad for any prior ## D5 Knowledge Base Output entry to avoid re-deriving known status.
2. Retirement Pass
For each item in OPEN_RESEARCH.md, check whether a matching synthesis doc exists in docs/research/. A match is any .md file whose title, slug, or frontmatter topic corresponds to the queue item. Do not infer a match — require a confirmed file.
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.
- 2d ago First seen · 134 lines · 35 tokens per session scan A ec50f19ee88c
D5 Knowledge Base is an agent published in the GitHub repository EndogenAI/dogma (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,496 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-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-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.
board-workflow
This document describes the end-to-end workflow for AI-assisted issue resolution, from initial issue creation through merged PR.
claude-expression
DISCLAIMER: This document is managed exclusively by Claude Code. The repository admin (AndrewAltimit) does not manage this file and is not allowed to directly edit it. Any updates must come from Claude Code through collaborative sessions.
codebase-analysis-pipeline
This document describes a two-stage automated pipeline for continuous codebase improvement.