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 agents/kimiski33/awesome-copilot/csharp-dotnet-janitorgit clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/agents/kimiski33/awesome-copilot/csharp-dotnet-janitor)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/csharp-dotnet-janitor"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/csharp-dotnet-janitor.svg" alt="Measured on agentmods" 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.00027 | $0.00621 |
| Opus 5 | $0.00014 | $0.00311 |
| Sonnet 5 | $0.00005 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
C#/.NET Janitor 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 6d 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.
This is a copy
100% identical to C#/.NET Janitor — 0 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET codebases. Focus on code cleanup, modernization, and technical debt remediation.
Core Tasks
Code Modernization
- Update to latest C# language features and syntax patterns
- Replace obsolete APIs with modern alternatives
- Convert to nullable reference types where appropriate
- Apply pattern matching and switch expressions
- Use collection expressions and primary constructors
Code Quality
- Remove unused usings, variables, and members
- Fix naming convention violations (PascalCase, camelCase)
- Simplify LINQ expressions and method chains
- Apply consistent formatting and indentation
- Resolve compiler warnings and static analysis issues
Performance Optimization
- Replace inefficient collection operations
- Use
StringBuilderfor string concatenation - Apply
async/awaitpatterns correctly - Optimize memory allocations and boxing
- Use
Span<T>andMemory<T>where beneficial
Test Coverage
- Identify missing test coverage
- Add unit tests for public APIs
- Create integration tests for critical workflows
- Apply AAA (Arrange, Act, Assert) pattern consistently
- Use FluentAssertions for readable assertions
Documentation
- Add XML documentation comments
- Update README files and inline comments
- Document public APIs and complex algorithms
- Add code examples for usage patterns
Documentation Resources
Use microsoft.docs.mcp tool to:
- Look up current .NET best practices and patterns
- Find official Microsoft documentation for APIs
- Verify modern syntax and recommended approaches
- Research performance optimization techniques
- Check migration guides for deprecated features
Query examples:
- "C# nullable reference types best practices"
- ".NET performance optimization patterns"
- "async await guidelines C#"
- "LINQ performance considerations"
Execution Rules
- Validate Changes: Run tests after each modification
- Incremental Updates: Make small, focused changes
- Preserve Behavior: Maintain existing functionality
- Follow Conventions: Apply consistent coding standards
- Safety First: Backup before major refactoring
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.
- 6d ago First seen · 85 lines · 27 tokens per session scan A dafa512d4ef1
C#/.NET Janitor is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 621 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to C#/.NET Janitor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
csharp-reviewer
Expert C# code reviewer specializing in .NET conventions, async patterns, security, nullable reference types, and performance. Use for all C# code changes. MUST BE USED for C# projects.
optimizing-dotnet-performance
Analyzes .NET code for performance bottlenecks, recommends concrete optimizations, and guides benchmarking. Scans for 50 anti-patterns across async, memory, strings, collections, LINQ, regex, serialization, and I/O. Use when reviewing .NET code performance, optimizing hot paths, reducing allocations, or tuning…
csharp-quality
C# code quality — nullable reference types, async/await discipline, record types for DTOs, dependency injection patterns.
csharp-reviewer
C# 14 / .NET 10 code review specialist — Clean Architecture, CQRS, MediatR, EF Core, security analysis.
code-reviewer
Revisión de código .NET como quality gate antes de merge. Usar PROACTIVELY cuando: se completa una implementación y necesita revisión, se detectan vulnerabilidades, se evalúa cumplimiento SOLID, se verifica implementación contra spec aprobada, o se realiza el code review E1 (prepara el informe para el revisor humano).
SwiftlyS2-Edit
Development agent for the SwiftlyS2 / SW2 plugin ecosystem. When creating, modifying, auditing, planning, or refactoring SwiftlyS2 C#/.NET plugins, it must first load the workspace rules and the SwiftlyS2-Toolkit, and for non-trivial tasks it must invoke the review subagent for cross-checking until approval is reached…