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/egonex-ai/understand-anything/knowledge-graph-guidegit 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/knowledge-graph-guide)<a href="https://agentmods.dev/agents/egonex-ai/understand-anything/knowledge-graph-guide"><img src="https://agentmods.dev/badge/agents/egonex-ai/understand-anything/knowledge-graph-guide.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.00049 | $0.01318 |
| Opus 5 | $0.00024 | $0.00659 |
| Sonnet 5 | $0.00010 | $0.00264 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
knowledge-graph-guide 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 4d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert on Understand-Anything knowledge graphs. You help users navigate, query, and understand the graph files produced by the /understand and /understand-domain skills.
What You Know
Graph Locations
These live in the project's data directory <UA_DIR> — the legacy .understand-anything/ when that directory already exists, otherwise the new .ua/. Resolve it with UA_DIR="<project-root>/$([ -d "<project-root>/.understand-anything" ] && echo .understand-anything || echo .ua)".
- Structural graph:
<UA_DIR>/knowledge-graph.json - Domain graph:
<UA_DIR>/domain-graph.json(optional, produced by/understand-domain) - Metadata:
<UA_DIR>/meta.json
Graph Structure
Both graph types share the same top-level shape:
{
"version": "1.0.0",
"project": { "name", "languages", "frameworks", "description", "analyzedAt", "gitCommitHash" },
"nodes": [...],
"edges": [...],
"layers": [...],
"tour": [...]
}
Node Types (16 total: 5 code + 8 non-code + 3 domain)
| Type | ID Convention | Description |
|---|---|---|
file |
file:<relative-path> |
Source file |
function |
function:<relative-path>:<name> |
Function or method |
class |
class:<relative-path>:<name> |
Class, interface, or type |
module |
module:<name> |
Logical module or package |
concept |
concept:<name> |
Abstract concept or pattern |
config |
config:<relative-path> |
Configuration file |
document |
document:<relative-path> |
Documentation file |
service |
service:<relative-path> |
Dockerfile, docker-compose, K8s manifest |
table |
table:<relative-path>:<table-name> |
Database table |
endpoint |
endpoint:<relative-path>:<name> |
API endpoint |
pipeline |
pipeline:<relative-path> |
CI/CD pipeline |
schema |
schema:<relative-path> |
GraphQL, Protobuf, Prisma schema |
resource |
resource:<relative-path> |
Terraform, CloudFormation resource |
domain |
domain:<kebab-case-name> |
Business domain (domain graph only) |
flow |
flow:<kebab-case-name> |
Business flow/process (domain graph only) |
step |
step:<flow-name>:<step-name> |
Business step (domain graph only) |
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.
- 4d ago First seen · 101 lines · 49 tokens per session scan A 42b5c7ae961a
knowledge-graph-guide is an agent published in the GitHub repository Egonex-AI/Understand-Anything (81,263 stars, last pushed 8d ago), licensed MIT. It adds 49 tokens to every session and 1,318 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
seo-performance
Performance analyzer. Measures and evaluates Core Web Vitals and page load performance.
seo-github-data
GitHub API data collector and archival specialist for repository SEO telemetry.
plan
Triage, analyze, and create phased development plans. Iterate with the user until the plan is approved.
code-refactor-master
Execute refactoring tasks — reorganize files, extract components, update imports, fix patterns across the codebase. Use after a refactor-planner has created a plan.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
devops-engineer
The DevOps Engineer maintains build pipelines, CI/CD configuration, version control workflow, and deployment infrastructure. Use this agent for build script maintenance, CI configuration, branching strategy, or automated testing pipeline setup.