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 commands/rylsherdamz-rgb/stellar-forge/graphifygit clone --depth 1 https://github.com/rylsherdamz-rgb/stellar-forgeWrote 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/commands/rylsherdamz-rgb/stellar-forge/graphify)<a href="https://agentmods.dev/commands/rylsherdamz-rgb/stellar-forge/graphify"><img src="https://agentmods.dev/badge/commands/rylsherdamz-rgb/stellar-forge/graphify.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.00000 | $0.00294 |
| Opus 5 | $0.00000 | $0.00147 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
graphify 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 5d 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.
What it actually says
/graphify
Build a knowledge graph of the current project or a specific path for navigation and querying.
Usage
/graphify [path] [options]
path: defaults to.(current project root)options:--no-viz,--mode deep,--update,--directed
What it does
- Detects all files in the project
- Extracts entities and relationships (AST for code, semantic for docs)
- Builds a knowledge graph with community detection
- Generates
graphify-out/with:graph.html— interactive visualizationGRAPH_REPORT.md— audit report with god nodes and surprising connectionsgraph.json— raw graph data for queries
After graphify
You can navigate the project:
/graphify query "How do the contracts connect to the frontend?"/graphify query "What's the payment flow?"/graphify explain "<node-name>"
Integration Points
- Run automatically after
/scaffoldto graph the new project - Run automatically after
/deployto graph the deployed project state - Run automatically after
/test-e2eto graph test artifacts - Part of Phase 0 (self-graphify the framework repo)
- Part of Phase 4.5 (graphify the user's generated project)
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.
- 5d ago First seen · 33 lines · 0 tokens per session scan A 3b4b6cfed474
graphify is a command published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 294 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-08-30.
Other commands, from other repositories
CODEBOT
Analyze code changes between current branch and main.
update
The update command updates the node's Docker images to their latest versions.
reset
The reset command resets a node, optionally including its configuration and data.
restart
The restart command stops and then starts a node, restarting all services.
setup
The setup command initializes a new Dash node with the specified configuration preset.
start
The start command launches a Dash node and its associated services.