graphify-dotnet

graphify-dotnet is a skill for Claude Code, Codex from managedcode/dotnet-skills. It costs 125 tokens per session (1,766 once invoked), scanned A, original, MIT.

A tool that turns a repository's source code into maps showing files, dependencies, and other relationships. It can export these maps as JSON, HTML, SVG, Cypher, Markdown, or Obsidian files.

In plain words
What is it for?
Use it for onboarding, architecture reviews, dependency discovery, repository snapshots, and sharing codebase maps.
Why use it?
It makes a large or unfamiliar codebase easier to understand than searching for individual files and symbols.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is graphify run . --format html,report --output ./artifacts/graph.

Good fit Use it for onboarding, architecture reviews, dependency discovery, repository snapshots, and sharing codebase maps.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/managedcode/dotnet-skills
agentmods
npx agentmods add skills/managedcode/dotnet-skills/graphify-dotnet

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for graphify-dotnet

README.md
[![agentmods](https://agentmods.dev/badge/skills/managedcode/dotnet-skills/graphify-dotnet.svg)](https://agentmods.dev/skills/managedcode/dotnet-skills/graphify-dotnet)
Your own site
<a href="https://agentmods.dev/skills/managedcode/dotnet-skills/graphify-dotnet"><img src="https://agentmods.dev/badge/skills/managedcode/dotnet-skills/graphify-dotnet.svg" alt="Measured on agentmods" height="20"></a>
Per session 125 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,766 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00125 $0.01766
Opus 5 $0.00063 $0.00883
Sonnet 5 $0.00025 $0.00353
Haiku 4.5 $0.00013 $0.00177

Measured 3d ago against content hash 907ccb7c6bc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

graphify-dotnet 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 3d 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.

catalog/Tools/Graphify/skills/graphify-dotnet/SKILL.md · 164 lines

How it starts

The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.

graphify-dotnet

Trigger On

  • graphify, graphify run, graphify watch, graphify benchmark, or graphify config
  • generating graph.json, graph.html, graph.svg, graph.cypher, GRAPH_REPORT.md, obsidian/, or wiki/
  • building onboarding maps, architecture snapshots, or dependency-discovery artifacts from a repository
  • choosing between AST-only extraction and AI-enriched semantic extraction
  • pushing graph output into Neo4j, Obsidian, wiki docs, or CI artifacts

Workflow

  1. Confirm the problem is structural discovery, architecture review, onboarding, or graph export. If the user only needs one symbol lookup, one bug fix, or one dependency trace, normal repo search and tests are cheaper than a full graph run.
  2. Install and verify the tool before doing anything else:
    dotnet --version
    dotnet tool install -g graphify-dotnet
    graphify --version
    
  3. Start with a bounded AST-only run so the first output is fast and deterministic:
    graphify run ./src --format json,html,report --provider none --verbose
    
  4. Review outputs in this order:
    • GRAPH_REPORT.md for quick signal
    • graph.html for visual exploration
    • graph.json for scripting and downstream tooling
  5. Add AI enrichment only when inferred relationships or conceptual grouping matter more than strict syntax-only structure.
  6. Expand export formats for the real consumer:
    • svg for static docs and PRs
    • neo4j for graph queries
    • obsidian,wiki for knowledge-base or onboarding flows
  7. Use watch for iterative architecture work, but rerun a clean run periodically because deletes and renames can leave stale references behind.
  8. Run benchmark only after you already trust the generated graph.json; its value is comparative token-reduction evidence, not billing-grade accounting.

Architecture

flowchart LR
  A["Repository or subtree"] --> B["graphify run / watch"]
  B --> C{"AI provider configured?"}
  C -->|No| D["AST extraction only"]
  C -->|Yes| E["AST + semantic extraction"]
  D --> F["Knowledge graph + Louvain communities"]
  E --> F
  F --> G{"Output target"}
  G -->|Human review| H["graph.html + GRAPH_REPORT.md"]
  G -->|Automation| I["graph.json"]
  G -->|Static docs| J["graph.svg"]
  G -->|Knowledge base| K["obsidian/ or wiki/"]
  G -->|Graph queries| L["graph.cypher for Neo4j"]

Read the full file on GitHub · 164 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 3d ago First seen · 164 lines · 125 tokens per session scan A 907ccb7c6bc4

Subscribe to this mod's changes

graphify-dotnet is a skill published in the GitHub repository managedcode/dotnet-skills (477 stars, last pushed 2d ago), licensed MIT. It adds 125 tokens to every session and 1,766 once invoked, about $0.0006 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-09-03.

Related

Other skills, from other repositories

pr-review

Multi-dimensional review of a PR or feature branch in microsoft/win-dev-skills. Activate on "review my PR / changes / branch", "vet before pushing", "PR review", "is this ready to merge". Fans out parallel sub-agents over skill content, the skill-vs-tool boundary (solution hierarchy), tool correctness…

microsoft/win-dev-skills · 98 tokens

winui-code-review

Code quality review for WinUI 3 apps — MVVM compliance, x:Bind correctness, accessibility, theming, security, and performance. Use before committing to catch issues that the compiler and UI tests won't find.

microsoft/win-dev-skills · 49 tokens

maf-anti-pattern-scanner

Scans a MAF 1.3.0 codebase for known anti-patterns AFTER migration is complete. Prefer the MCP tool MafScanAntiPatterns for one-shot scans; this skill is for understanding the rule taxonomy or contributing new anti-pattern rules. Detects insecure credential usage (DefaultAzureCredential, hard-coded keys), unsafe…

joslat/maf-doctor · 130 tokens

review

Review a change for correctness, quality, and guideline compliance using a library of specialized reviewer roles. Use before opening a PR, after finishing a chunk of work, or to review an existing PR. Two output modes — a local severity-ranked report for a fix loop (default), or inline GitHub comments (--comment).…

ronaknnathani/relay · 83 tokens

open-pr

Stage, commit, push, and open a pull request following the author's repository and AGENTS.md conventions — repo-style commit messages, a prose PR summary, and a Testing Done command list. Use when work is finished and the caller wants it committed and a PR opened. Supports --draft and an optional local review before…

ronaknnathani/relay · 68 tokens

simplify

Reduce complexity in recently changed code — cut needless abstraction, dead code, and duplication; improve names and structure — WITHOUT changing behavior. Quality only; it does not hunt for bugs (use review for that). Use after implementing a chunk of work, before review, or whenever a diff feels more complicated…

ronaknnathani/relay · 108 tokens