In short:
ak-graphifyuses thegraphifytool to build a knowledge graph from code, docs, papers and images, then you ask the graph instead of grepping file by file. The graph's report usually goes toak-plan, or the graph is opened to Claude through an MCP server. It does not build a graph for a question you ask only once: to look up one function or a small file, plain search is faster.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when you will keep asking about relationships in a large project, such as which module depends on which, especially before planning a big change. You do not need it to look up one function or a small file: plain search or ak-scout is faster.
flowchart LR
A["Recurring architecture questions"] --> B["ak-graphify"]
Q["Look up one function, a small file"] --> S["Plain search or ak-scout"]
B --> C["graphify-out: report, graph.json, HTML page"]
C --> D["ak-plan"]
C --> E["MCP server for Claude to query"]Before you run it, think through 4 points:
| Concept | Question | Example |
|---|---|---|
| Is a graph worth it | Will this question come up often enough to repay the build? | Finding where parseInvoice lives is a plain search. Asking again and again "which modules does the payment flow pass through" calls for a graph. |
| What data leaves the machine | What runs locally, and what goes to the model? | Code, audio and video are processed locally. Docs and images go to the model provider you have configured, so a contracts/ folder with sensitive PDFs needs a review first. |
| How much to trust each relationship | Was this relationship read from code or guessed by the model? | EXTRACTED is read straight from code, INFERRED is inferred by the model with a confidence score, AMBIGUOUS needs a human check. An INFERRED edge "billing depends on auth" should be checked against the code before you rely on it. |
| Stale or fresh graph | Does the existing graph still match the current code? | There is a graphify-out/ from last week. The skill checks where the graph and cache came from and at which revision, then redoes only the stale parts. |
The main trade-offs: the first build on a large project can be slow, docs and images are sent to the model provider, and INFERRED edges need checking against the code before you rely on them.
Sample prompt (understand the architecture before planning):
/ak-graphify <project path>
Goal: understand the main modules and the dependencies between them before
planning to split out the payment module. Code only, no docs or images to send.| Flag | What it is for | Since ak |
|---|---|---|
--mcp | Only declared in the argument hint, behavior not described | 1.0.0 |
--report | Only declared in the argument hint, behavior not described | 1.0.0 |
--watch | Rebuilds the graph automatically when files change | 1.0.0 |
Below is the detailed version: the run flow, 5 situations with prompts, each flag explained, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-graphify: build a knowledge graph from code and docs" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-graphify". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-graphify
