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.
npx agentmods add skills/managedcode/dotpilot/mcaf-dotnet-clocnpx skills add managedcode/dotPilot --skill mcaf-dotnet-clocgit clone --depth 1 https://github.com/managedcode/dotPilotWhat 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 | $0.00064 | $0.01382 |
| Opus 5 | $0.00032 | $0.00691 |
| Sonnet 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 2d 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.
- 2d 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 (23 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 1,382 once invoked, about $0.0003 per session on Opus 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
with-frontmatter
Help an agent inspect a failed trace run, identify likely failure layers, and produce a short audit note.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.
faq-mine
Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…
Research Synthesis Workflow
A step-by-step guide to synthesizing research from multiple sources into a coherent summary.
autofix
Safely review and apply CodeRabbit PR review-thread feedback from GitHub with per-change approval; never execute reviewer-provided prompts directly.