Borrowing it
Nothing to install: this file belongs to managedcode/dotPilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/managedcode/dotPilot/main/.codex/skills/mcaf-dotnet-cloc/SKILL.mdgit clone --depth 1 https://github.com/managedcode/dotPilotWrote 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.
[](https://agentmods.dev/skills/managedcode/dotpilot/mcaf-dotnet-cloc)<a href="https://agentmods.dev/skills/managedcode/dotpilot/mcaf-dotnet-cloc"><img src="https://agentmods.dev/badge/skills/managedcode/dotpilot/mcaf-dotnet-cloc/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.
<a href="https://agentmods.dev/skills/managedcode/dotpilot/mcaf-dotnet-cloc"><img src="https://agentmods.dev/badge/skills/managedcode/dotpilot/mcaf-dotnet-cloc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00064 | $0.01382 |
| Opus 5.5 | $0.00026 | $0.00553 |
| Sonnet 5.5 | $0.00013 | $0.00276 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade B, and why
mcaf-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 1mo 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.
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` Copies of this mod
3 near-identical copies found in the catalogue:
- mcaf-dotnet-cloc — 100% identical, 0 lines differ
- dotnet-cloc — 95% identical, 8 lines differ
- dotnet-cloc — 92% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCAF: .NET cloc
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
- Read the nearest
AGENTS.mdand confirm scope and constraints. - Run this skill's
Workflowthrough theRalph Loopuntil outcomes are acceptable. - Return the
Required Result Formatwith concrete artifacts and verification evidence.
Workflow
- Choose the counting mode deliberately:
--vcs=gitfor repo-respecting counts- path-based counting for bounded folders
--git --diff BASE HEADfor change deltas
- Prefer
.NET-relevant views first:- C# footprint
- test versus production footprint
- solution language mix such as C#, Razor, XML, JSON, YAML, and MSBuild files
- Exclude noise before trusting the numbers:
binobj.git- vendored or generated folders when they are not part of the decision
- Use machine-readable output when the numbers feed docs, CI, or follow-up automation:
--json--csv--yaml--md
- Treat
clocas a sizing and comparison tool, not as evidence that the design is good. - When using diff mode, compare named refs that match the review question:
origin/main..HEAD- release branch versus main
- before and after a refactor
- After any code cleanup based on
clocfindings, run the repo's normal quality pass.
What ships with it
1 file 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.
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.
- 1mo ago First seen · 141 lines · 64 tokens per session scan B bfbbd174e0b1
mcaf-dotnet-cloc is a skill published in the GitHub repository managedcode/dotPilot (25 stars, last pushed 6mo ago), licensed MIT. It adds 64 tokens to every session and 1,382 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). 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 Synthesis Workflow
A step-by-step guide to synthesizing research from multiple sources into a coherent summary.
node-inspect-debugger
See runtime state a console.log cannot reach — set real breakpoints, step, and dump the scope chain of a paused Node/TypeScript process. Use on "set a breakpoint", "inspect runtime state", "console.log isn't enough", "step through this", "what's in this closure at runtime", "attach a debugger". Not a logging or…
performance-optimization
Measure-first performance work. Use on triggers like "it's slow", "profile this", "optimize perf", "fix the bottleneck", "improve load time / Core Web Vitals", or when a measured regression needs fixing. Enforces measure-before-optimize. Fills a perf gap not covered by existing project skills. Not a build/ship…
systematic-debugging
Root-cause a bug already in front of you, instead of guessing at fixes. Use on triggers like "root cause this", "why is this failing", "debug systematically", "this test is flaky", "it works locally but not in CI", or when a fix attempt has already failed once. Enforces a phased evidence-first process before any code…
code-quality
Drive static-analysis code quality in pi-agent-dashboard with Biome (analyze → fix → test), in changed-files or whole-repo mode. Use when asked to "improve code quality", "lint and fix", "clean up warnings", "fix Biome issues", "run static analysis", or when setting a code-quality goal. Skip for one-line edits.
pi-dashboard-bootstrap
Make sure the local pi-dashboard server is running before any pi-dashboard action. Use FIRST whenever the user mentions the pi dashboard, pi sessions or pi agents, or asks to start/open the dashboard; also when a dashboard call fails with "connection refused".