Orleans.RateLimiting: Skill for Codex

.codex/skills/graphify-dotnet/SKILL.md

graphify-dotnet is a skill for Codex from managedcode/Orleans.RateLimiting. It costs 45 tokens per session (1,673 once invoked), scanned A, a copy of graphify-dotnet, MIT.

A tool for generating maps of a codebase, showing its files, dependencies, and other relationships. It supports .NET and mixed-language repositories and can export reports, diagrams, and data for tools such as Neo4j or Obsidian.

In plain words
What is it for?
Use it to create architecture snapshots, explore dependencies, build onboarding documentation, or export a repository graph for further analysis.
Why use it?
It helps when a repository is too large or unfamiliar to understand through individual file searches. The maps support architecture reviews, onboarding, and finding how parts of the system connect.

Skill for Codex

Written for Codex: installed under .codex/.

This is managedcode/Orleans.RateLimiting's own configuration. It tells Codex how to work on Orleans.RateLimiting itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Orleans.RateLimiting configures →

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.

Reuse

Borrowing it

Nothing to install: this file belongs to managedcode/Orleans.RateLimiting. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/managedcode/Orleans.RateLimiting/main/.codex/skills/graphify-dotnet/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/managedcode/Orleans.RateLimiting

Made for: 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/orleans.ratelimiting/graphify-dotnet/github.svg)](https://agentmods.dev/skills/managedcode/orleans.ratelimiting/graphify-dotnet)
Your own site
<a href="https://agentmods.dev/skills/managedcode/orleans.ratelimiting/graphify-dotnet"><img src="https://agentmods.dev/badge/skills/managedcode/orleans.ratelimiting/graphify-dotnet/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for graphify-dotnet

Your own site · 80×15
<a href="https://agentmods.dev/skills/managedcode/orleans.ratelimiting/graphify-dotnet"><img src="https://agentmods.dev/badge/skills/managedcode/orleans.ratelimiting/graphify-dotnet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,673 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 92% copy Near-identical to another mod 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.00045 $0.01673
Opus 5.5 $0.00018 $0.00669
Sonnet 5.5 $0.00009 $0.00335
Haiku 4.5 $0.00005 $0.00167

Measured 19d ago against content hash d9138a1de09e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-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 19d 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.

Origin

This is a copy

92% identical to graphify-dotnet — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.codex/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. 19d ago First seen · 164 lines · 45 tokens per session scan A d9138a1de09e

Subscribe to this mod's changes

graphify-dotnet is a skill published in the GitHub repository managedcode/Orleans.RateLimiting (30 stars, last pushed 11d ago), licensed MIT. It adds 45 tokens to every session and 1,673 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to graphify-dotnet, differing in 6 lines, and is treated as a copy.

Related

Other skills, from other repositories

generate-code-cs

Generate the code from typespec for C#. Parameter: C# SDK repository root location .

Azure/azure-sdk-for-net · 26 tokens

author-test

Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.

Azure/azure-sdk-for-net · 68 tokens

opentelemetry-net-instrumentation

Provides guidance for implementing OpenTelemetry instrumentation in .NET codebases, covering tracing (Activities/Spans), metrics, logs, naming conventions, error handling, performance, SDK setup, resources, context propagation, and API design best practices.

Aaronontheweb/dotnet-skills · 56 tokens

migrate-xunit-to-mstest

Convert .NET tests from xUnit.net v2/v3 to MSTest v4 while preserving VSTest or MTP. Use for replacing xunit packages, Fact/Theory/InlineData/MemberData, assertions, IClassFixture/ICollectionFixture, ITestOutputHelper, TestContext cancellation, traits/Owner, skips, timeouts, and xUnit parallelization. Also use when a…

managedcode/dotnet-skills · 141 tokens

migrate-xunit-to-xunit-v3

Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…

managedcode/dotnet-skills · 149 tokens

wpf

Build and modernize WPF applications on .NET with correct XAML, data binding, commands, threading, styling, and Windows desktop migration decisions. USE FOR: working on WPF UI, MVVM, binding, commands, or desktop modernization; migrating WPF from .NET Framework to .NET; integrating newer Windows capabilities into a…

managedcode/dotnet-skills · 122 tokens