dotnet-structure

dotnet-structure is a command for coding agents from mathisk2095/jko-claude-plugins. It costs 24 tokens per session (466 once invoked), scanned A, original, MIT.

A review of a .NET backend’s solution and folder layout. It examines projects, layers, file sizes, and the boundaries between parts of the application.

In plain words
What is it for?
Use it to review a .NET solution, project, or directory and get suggestions for organizing projects, folders, files, and architectural layers.
Why use it?
It helps find tangled dependencies, misplaced responsibilities, oversized files, and structures that make a codebase harder to understand or change.

Command

Part of the dotnet-backend plugin — 1 skill, 4 commands shipped together

Install

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.

agentmods
npx agentmods add commands/mathisk2095/jko-claude-plugins/dotnet-structure
Clone the repo
git clone --depth 1 https://github.com/mathisk2095/jko-claude-plugins

Or install dotnet-backend, the plugin that ships this one along with the rest of its 1 skill, 4 commands.

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 dotnet-structure

README.md
[![agentmods](https://agentmods.dev/badge/commands/mathisk2095/jko-claude-plugins/dotnet-structure.svg)](https://agentmods.dev/commands/mathisk2095/jko-claude-plugins/dotnet-structure)
Your own site
<a href="https://agentmods.dev/commands/mathisk2095/jko-claude-plugins/dotnet-structure"><img src="https://agentmods.dev/badge/commands/mathisk2095/jko-claude-plugins/dotnet-structure.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 466 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00024 $0.00466
Opus 5 $0.00012 $0.00233
Sonnet 5 $0.00005 $0.00093
Haiku 4.5 $0.00002 $0.00047

Measured 3d ago against content hash 5b1458bdaa03, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dotnet-structure 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.

plugins/dotnet-backend/commands/dotnet-structure.md · 57 lines

What it actually says

Analyze the .NET backend structure. If $ARGUMENTS is provided, analyze that solution, directory, or project. Otherwise auto-detect the main backend solution.

First: Use the dotnet-backend-expert skill. Read references/project-structure.md and references/architecture.md.

Analysis Steps

  1. Map the solution:
    • list *.sln and *.csproj
    • classify projects as API/host, AppHost, contracts, application, domain, infrastructure, workers, tests
    • detect whether the codebase is layered, vertical slice, modular monolith, or tangled
  2. File size audit:
    • flag .cs files over 300 lines as split candidates
    • flag .cs files over 500 lines as urgent
    • suggest the split by responsibility, not by arbitrary regions
  3. Project boundary audit:
    • domain should not depend on infrastructure or host projects
    • contracts should stay transport-safe
    • AppHost should orchestrate, not contain business rules
  4. Folder organization audit:
    • check for one major type per file
    • check for feature grouping versus giant technical buckets
    • check whether endpoints, services, repositories, entities, and contracts are easy to locate
  5. Missing pieces:
    • missing contracts project or folder
    • missing application/service boundary
    • missing test projects
    • missing composition root extensions

Output

Current Structure

Show a tree with project purpose and notable line counts.

Structure Score: X/10

Explain the score briefly.

Issues Found

Order by impact. For each issue include the exact project/file and the recommended move, split, or create action.

Recommended Target Layout

If a change is needed, show the ideal target shape for this backend.

Migration Steps

Give a safe incremental path that keeps the app working at each step.

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 · 57 lines · 24 tokens per session scan A 5b1458bdaa03

Subscribe to this mod's changes

dotnet-structure is a command published in the GitHub repository mathisk2095/jko-claude-plugins (3 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 466 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-31.