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 skills/lucasduys/forge/graphify-integrationnpx skills add LucasDuys/forge --skill graphify-integrationgit clone --depth 1 https://github.com/LucasDuys/forgeWhat 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.00028 | $0.01656 |
| Opus 5 | $0.00014 | $0.00828 |
| Sonnet 5 | $0.00006 | $0.00331 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
graphify-integration 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Graphify Integration Skill
This skill enables Forge to leverage codebase knowledge graphs for architecture-aware planning and research. When a graphify knowledge graph exists (or can be generated), Forge agents use it to understand code structure, discover dependencies, prioritize tasks, and reduce context size.
Prerequisites
Graphify integration is optional but recommended for projects with:
- 20+ source files
- Multiple modules or packages
- Cross-component dependencies
- Unfamiliar codebases (new contributor scenario)
Installation
Graphify is bundled as part of Forge's tool ecosystem. Install via:
pip install graphifyy
Or use /forge setup-tools which detects and offers to install graphify automatically.
Detection and Auto-Build
At the start of /forge plan or /forge execute, the commands auto-detect and build:
# Check if graphify is installed
node scripts/forge-tools.cjs graph-status
# If installed and no graph exists, build one automatically
node scripts/forge-tools.cjs graph-build --project-dir .
# Extract summary for planning context (god nodes, communities, stats)
node scripts/forge-tools.cjs graph-summary --graph graphify-out/graph.json
The build runs graphify . which processes the codebase through: detect -> extract (tree-sitter AST) -> build (NetworkX) -> cluster (Leiden) -> analyze -> export. Output goes to graphify-out/ (graph.json, graph.html, GRAPH_REPORT.md).
Never block on graph availability. If graphify is not installed or the build fails, all commands proceed with standard behavior.
CLI Commands
Agents use these node one-liners to query the graph (no Python needed at query time):
| Command | Purpose |
|---|---|
graph-status |
Check if graphify CLI is installed |
graph-build --project-dir . |
Build knowledge graph from codebase |
graph-summary --graph graphify-out/graph.json |
Get god nodes, communities, stats |
graph-query --graph graphify-out/graph.json --term "auth" |
Search for nodes matching a term |
graph-dependents --graph graphify-out/graph.json --file "src/auth.ts" |
Find all files that depend on a file |
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 · 219 lines · 28 tokens per session scan A 5fa47c030e12
graphify-integration is a skill published in the GitHub repository LucasDuys/forge (55 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,656 once invoked, about $0.0001 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 skills, from other repositories
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
survey-design
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).
design-critique
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use heuristic-evaluation (prototyping-testing).
design-sprint-plan
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use team-workflow.
handoff-spec
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).
team-workflow
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.