Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/dynamic-agent-navigation)<a href="https://agentmods.dev/agents/endogenai/dogma/dynamic-agent-navigation"><img src="https://agentmods.dev/badge/agents/endogenai/dogma/dynamic-agent-navigation.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.1 | $0.00000 | $0.02729 |
| Opus 5 | $0.00000 | $0.01365 |
| Sonnet 5 | $0.00000 | $0.00546 |
| Haiku 4.5 | $0.00000 | $0.00273 |
Grade A, and why
dynamic-agent-navigation 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynamic AI Agent Navigation: Graph Routing Algorithms for Decision Workflows
Research question: Is it feasible to replace static "if/then" decision trees in agent workflows with navigable weighted knowledge graphs, enabling classical routing algorithms (A*, Dijkstra) to determine the most efficient, cost-effective, or reliable path to a goal state?
Date: 2026-03-14 Research Issue: #203 Related:
data/phase-gate-fsm.yml(endogenous FSM);data/delegation-gate.yml(endogenous routing table);docs/research/endogenic-design-paper.md(H1, H4 framework)
Executive Summary
Graph routing algorithms — A*, Dijkstra, shortest-path traversal — are a natural fit for agent navigation when workflow state can be encoded as a weighted directed graph. This synthesis evaluates three architectural options (LangGraph, NetworkX, and native FSM/YAML) against the three core research questions from issue #203: state-as-coordinates, dynamic weighting, and Markdown-to-Graph schema design.
Key finding: This codebase already instantiates the core primitives. data/phase-gate-fsm.yml
is a working navigable state graph; data/delegation-gate.yml is a working routing table.
The highest-value next step is not adopting LangGraph, but extending these endogenous artifacts
with edge weights and a NetworkX-backed path-analysis script.
The Algorithms Before Tokens axiom (MANIFESTO.md §2) is directly instantiated by this
approach: encoding workflow routing as a data structure (YAML graph) that a deterministic
algorithm can traverse is strictly superior to re-deriving routing logic via token burn each
session.
Hypothesis Validation
H1 — State-as-Coordinates is tractable with existing FSM artifacts
Hypothesis: An agent's current "position" in a workflow can be represented as a coordinate in a multi-dimensional state space, enabling graph-based navigation.
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 · 256 lines · 0 tokens per session scan A f7a98d3beffd
dynamic-agent-navigation is an agent published in the GitHub repository EndogenAI/dogma (2 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,729 tokens. 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-09-03.
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-implementer
AgentCortex /implement phase executor. Use when delegating implementation work that must follow agentic-os gates, evidence requirements, and skill injection.
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.