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 skills add CodeAlive-AI/ai-driven-development --skill refactoring-csharpgit clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-developmentWrote 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/codealive-ai/ai-driven-development/refactoring-csharp)<a href="https://agentmods.dev/skills/codealive-ai/ai-driven-development/refactoring-csharp"><img src="https://agentmods.dev/badge/skills/codealive-ai/ai-driven-development/refactoring-csharp/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/codealive-ai/ai-driven-development/refactoring-csharp"><img src="https://agentmods.dev/badge/skills/codealive-ai/ai-driven-development/refactoring-csharp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.02358 |
| Opus 5.5 | $0.00024 | $0.00943 |
| Sonnet 5.5 | $0.00012 | $0.00472 |
| Haiku 4.5 | $0.00006 | $0.00236 |
Grade A, and why
refactoring-csharp 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactoring C# Symbols
This skill ships a Roslyn-based C# rename CLI in src/. It is intentionally one-shot and
stateless: one call resolves the target, validates the request, and returns either a preview
or an applied rename. There is no public prepare step.
Contents
- Canonical CLI
- Contract
- How To Use It
- Monorepo Directory Mode
- Important Behavioral Rules
- Supported Targets
- File Rename Nuance
- Error Handling
- Success Criteria
- Recommended Output Style
Canonical CLI
If the skill was installed by install.sh, prefer the prebuilt CLI:
bin/csharp-refactor rename-symbol <sln|slnx|directory> <file> <line> <oldName> <newName> [dryRun=false|true]
Otherwise run the bundled source CLI from the skill directory:
dotnet run --project src/CSharpRefactoring.Cli -- rename-symbol <sln|slnx|directory> <file> <line> <oldName> <newName> [dryRun=false|true]
When invoked from outside the skill directory, use an absolute project path:
/<skill-dir>/bin/csharp-refactor rename-symbol <sln|slnx|directory> <file> <line> <oldName> <newName> [dryRun=false|true]
# or, if no prebuilt binary is installed:
dotnet run --project /path/to/refactoring-csharp/src/CSharpRefactoring.Cli -- rename-symbol <sln|slnx|directory> <file> <line> <oldName> <newName> [dryRun=false|true]
The tool project may create normal bin/ and obj/ directories under the skill. That is
expected and useful: it lets repeated runs reuse the .NET build cache instead of rebuilding
the CLI from scratch.
The target solution is not redirected to a temporary build output. The CLI opens the solution
from the solution directory and lets Roslyn/MSBuild use the target project's normal build
cache (obj/, bin/, or the repository's configured artifacts layout). This is intentional:
it avoids creating a second cache tree for the project being refactored and lets repeated
renames benefit from the project's existing MSBuild/Roslyn design-time build cache.
What ships with it
22 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.
- .gitignore 44 B
- install.ps1 11 KB runs code
- install.sh 11 KB runs code
- README.md 5.2 KB
- release.sh 2.7 KB runs code
- src/CSharpRefactoring.Cli/CSharpRefactoring.Cli.csproj 403 B
- src/CSharpRefactoring.Cli/Program.cs 4.2 KB
- src/CSharpRefactoring.Cli/sample/SampleTarget/Program.cs 451 B
- src/CSharpRefactoring.Cli/sample/SampleTarget/SampleRenameDemo.sln 973 B
- src/CSharpRefactoring.Cli/sample/SampleTarget/SampleRenameDemo.slnx 64 B
- src/CSharpRefactoring.Cli/sample/SampleTarget/SampleTarget.csproj 161 B
- src/CSharpRefactoring.Core.Tests/CSharpRefactoring.Core.Tests.csproj 1.0 KB
- src/CSharpRefactoring.Core.Tests/CSharpSymbolRenamerTests.cs 15 KB
- src/CSharpRefactoring.Core/CSharpRefactoring.Core.csproj 587 B
- src/CSharpRefactoring.Core/CSharpSymbolRenamer.cs 42 KB
- src/CSharpRefactoring.Core/DotNetSolutionsMerger/SolutionMerger.cs 32 KB
- src/CSharpRefactoring.slnx 255 B
- src/TestData/SampleRenameDemo/Program.cs 451 B
- src/TestData/SampleRenameDemo/SampleRenameDemo.csproj 161 B
- src/TestData/SampleRenameDemo/SampleRenameDemo.sln 973 B
- src/TestData/SampleRenameDemo/SampleRenameDemo.slnx 64 B
- src/TestData/SampleRenameDemo/SampleTarget.csproj 161 B
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 · 172 lines · 60 tokens per session scan A 57f1e7d54a79
refactoring-csharp is a skill published in the GitHub repository CodeAlive-AI/ai-driven-development (163 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 2,358 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
dotnet-maui-wpf-desktop
Production architectural patterns, MVVM clean architecture, async thread synchronization, high-performance UI rendering, native interop, and memory optimization for enterprise Windows and cross-platform desktop applications using WPF, .NET MAUI, and Windows App SDK.
unity-csharp-architecture-and-ecs
Architectural patterns, Data-Oriented Technology Stack (DOTS), Unity ECS, Burst Compiler, C# Job System, memory management, zero-allocation C# patterns, and frame-budget optimization for high-performance Unity game development.
writing-csharp
Idiomatic C# /.NET development. Use when writing C# code, changing .csproj or .sln, or working on ASP.NET Core apps, libraries, CLIs, workers, and xUnit/NUnit/MSTest suites. Emphasizes nullable references, async/await, boundary validation, focused dotnet feedback, and minimal dependencies. NOT for Go, Python…
godot-gdscript-patterns
Enterprise architecture patterns for Godot Engine 4.x using GDScript and C#, Node tree composition, Custom Resources, Signal Bus patterns, Direct Server APIs (PhysicsServer, RenderingServer), memory management, and performance profiling.
agent-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.
dotnet-backend-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting pure .NET backend code for Kestrel-hosted services. It provides expert critique for REST endpoints, SignalR hubs, TypeScript/React client integration shape, pragmatic Rust interop, application services, AppHost-aware project…