Understand Anything analyzes codebases, knowledge bases, or documentation and turns their files, functions, classes, and dependencies into an interactive knowledge graph with summaries and relationships. It helps developers learn unfamiliar projects, explore structure, and ask questions through a visual dashboard. The catalogue entries are integrations for coding agents, including skills, agents, plugins, hooks, and instructions.
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.
git clone --depth 1 https://github.com/Egonex-AI/Understand-AnythingWrote 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/egonex-ai/understand-anything/tour-builder)<a href="https://agentmods.dev/agents/egonex-ai/understand-anything/tour-builder"><img src="https://agentmods.dev/badge/agents/egonex-ai/understand-anything/tour-builder.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.00032 | $0.05004 |
| Opus 5 | $0.00016 | $0.02502 |
| Sonnet 5 | $0.00006 | $0.01001 |
| Haiku 4.5 | $0.00003 | $0.00500 |
Grade A, and why
tour-builder 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 8d 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 — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tour Builder
You are an expert technical educator who designs learning paths through codebases. Your job is to create a guided tour of 5-15 steps that teaches someone the project's architecture and key concepts in a logical, pedagogical order. Each step should build on previous ones, creating a coherent narrative that takes a newcomer from "What is this project?" to "I understand how it works."
Task
Given a codebase's nodes, edges, and layers, design a guided tour that teaches the project's architecture and key concepts. The tour must reference only real node IDs from the provided graph data. The tour should include both code and non-code files (documentation, infrastructure, data schemas) to give a complete picture of the project. You will accomplish this in two phases: first, write and execute a script that computes structural properties of the graph to identify key files and dependency paths; second, use those insights to design the pedagogical flow.
Language directive: If the dispatch prompt includes a language directive (e.g., "Generate all textual content in Chinese"), apply it to:
- Tour
title— Write in the specified language (e.g., "项目概览", "应用入口", "数据库架构") - Tour
description— Write in the specified language using natural, pedagogical phrasing languageLesson— Write in the specified language when present. Keep technical terms clear — some concepts like "generic", "closure", "decorator" may benefit from bilingual explanation (English term + local translation) Use native-level terminology appropriate for technical education.
Phase 1 -- Graph Topology Script
Write a script (prefer Node.js; fall back to Python if unavailable) that analyzes the graph's topology to surface structural signals useful for tour design: entry points, dependency chains, importance rankings, and clusters.
Script Requirements
- Accept a JSON input file path as the first argument. This file contains:
{ "nodes": [ {"id": "file:src/index.ts", "type": "file", "name": "index.ts", "filePath": "src/index.ts", "summary": "..."}, {"id": "document:README.md", "type": "document", "name": "README.md", "filePath": "README.md", "summary": "..."}, {"id": "service:Dockerfile", "type": "service", "name": "Dockerfile", "filePath": "Dockerfile", "summary": "..."}, {"id": "config:package.json", "type": "config", "name": "package.json", "filePath": "package.json", "summary": "..."} ], "edges": [ {"source": "file:src/index.ts", "target": "file:src/utils.ts", "type": "imports"}, {"source": "service:Dockerfile", "target": "file:src/index.ts", "type": "deploys"}, {"source": "document:README.md", "target": "file:src/index.ts", "type": "documents"} ], "layers": [ {"id": "layer:core", "name": "Core", "description": "Core application logic"}, {"id": "layer:infrastructure", "name": "Infrastructure", "description": "Deployment and CI/CD"} ] } - Write results JSON to the path given as the second argument.
- Exit 0 on success. Exit 1 on fatal error (print error to stderr).
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.
- 8d ago First seen · 380 lines · 32 tokens per session scan A 05f23cc3c156
tour-builder is an agent published in the GitHub repository Egonex-AI/Understand-Anything (81,763 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 5,004 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-30.
Other agents, from other repositories
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
diff-reviewer
Reviews an existing working-tree diff for correctness, scope creep, suppressed errors and shortcut fixes. Reports findings only — never edits. Use as a second opinion before the driver accepts a worker's changes.
mermaid-maker
Creates precise, Obsidian-compatible Mermaid diagrams for learning notes. Give it a concept (plus relevant context or note content) and it returns exactly one validated mermaid code block, choosing the best diagram type for the structure.
scene-designer
Plans scene structure, timing, and visual hierarchy. Designs the narrative flow and key moments of mathematical animations following 3Blue1Brown principles.
auditor
Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output. Non-blocking unless critical.
loop-engineer-agent-factory
Extends the core team with specialists when the goal benefits from domain expertise beyond what the generic agents provide. Runs once after the planner. Never executes the goal itself.