dotnet-cloc

A code-counting tool for .NET repositories, which are projects built with Microsoft’s .NET platform. It reports lines of code, the mix of programming languages, and differences between branches or other code versions.

In plain words
What is it for?
Use it to report C# and solution size, compare code changes between branches, and track code, tests, documentation, configuration, or CI changes in local workflows and CI.
Why use it?
It gives a repeatable way to measure a .NET codebase and see what changed between versions. This avoids relying on rough estimates or manually counting files.

Skill for Claude CodeCodex

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 skills/managedcode/mcpgateway/dotnet-cloc
Any agent
npx skills add managedcode/MCPGateway --skill dotnet-cloc
Clone the repo
git clone --depth 1 https://github.com/managedcode/MCPGateway

Made for: Claude Code, Codex.

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,390 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin 95% 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 $0.00062 $0.01390
Opus 5 $0.00031 $0.00695
Sonnet 5 $0.00012 $0.00278
Haiku 4.5 $0.00006 $0.00139

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

Security

Grade B, and why

dotnet-cloc scanned grade B with 1 finding 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 yesterday.

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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Debian or Ubuntu: `sudo apt install cloc`
Origin

This is a copy

95% identical to mcaf-dotnet-cloc — 8 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/dotnet-cloc/SKILL.md · 143 lines

How it starts

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

CLOC for .NET Repositories

Trigger On

  • the repo wants cloc
  • the team needs repeatable LOC, language, or branch diff statistics for a .NET repo
  • the user asks about C# codebase size, solution composition, or code-count deltas between refs

Value

  • produce a concrete project delta: code, docs, config, tests, CI, or review artifact
  • reduce ambiguity through explicit planning, verification, and final validation skills
  • leave reusable project context so future tasks are faster and safer

Do Not Use For

  • judging developer productivity from raw LOC
  • replacing behavioral verification, architecture review, or complexity analysis
  • counting generated or vendored files without an explicit reason

Inputs

  • the nearest AGENTS.md
  • target repository, solution, project, or subtree
  • the question being answered: footprint, composition, diff, or trend

Quick Start

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Choose the counting mode deliberately:
    • --vcs=git for repo-respecting counts
    • path-based counting for bounded folders
    • --git --diff BASE HEAD for change deltas
  2. Prefer .NET-relevant views first:
    • C# footprint
    • test versus production footprint
    • solution language mix such as C#, Razor, XML, JSON, YAML, and MSBuild files
  3. Exclude noise before trusting the numbers:
    • bin
    • obj
    • .git
    • vendored or generated folders when they are not part of the decision
  4. Use machine-readable output when the numbers feed docs, CI, or follow-up automation:
    • --json
    • --csv
    • --yaml
    • --md
  5. Treat cloc as a sizing and comparison tool, not as evidence that the design is good.
  6. When using diff mode, compare named refs that match the review question:
    • origin/main..HEAD
    • release branch versus main
    • before and after a refactor
  7. After any code cleanup based on cloc findings, run the repo's normal quality pass.

Read the full file on GitHub · 143 lines

Files

What ships with it

4 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. yesterday First seen · 143 lines · 62 tokens per session scan B 3a03d97131e3

Subscribe to this mod's changes

dotnet-cloc is a skill published in the GitHub repository managedcode/MCPGateway (5 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 1,390 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 95% identical to mcaf-dotnet-cloc, differing in 8 lines, and is treated as a copy.