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/codealive-ai/ai-driven-development/refactoring-csharpnpx skills add CodeAlive-AI/ai-driven-development --skill refactoring-csharpgit clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-developmentWhat 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.00060 | $0.02358 |
| Opus 5 | $0.00030 | $0.01179 |
| Sonnet 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 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.
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.
- yesterday 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 (131 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 2,358 once invoked, about $0.0003 per session on Opus 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
map-debug
Structured MAP debugging via task-decomposer, actor, and monitor agents. Use when reproducing a bug, isolating a regression, or diagnosing an error with specialized agents — including failing or flaky tests (pytest AssertionError), crashes and segmentation faults, memory-corruption or memory errors in native/C…
map-learn
Capture reusable lessons after a completed MAP workflow. Use when a MAP run has finished and you want rules written to .claude/rules/learned/ from a workflow summary or handoff. Do NOT use during active implementation.
map-task
Execute a single subtask from an existing MAP plan via Actor and Monitor. Use when map-plan has decomposed work and you want fine-grained control over one subtask. Do NOT use without an existing plan; run map-plan first.
map-explain
Deep walkthrough of code, a diff, or the whole project — problem, entities, flow, load-bearing-line rationale, side effects, assumptions, breakage. Use when learning unfamiliar code or auditing a diff.
map-auto
Single-entry autonomous autopilot: routes a task through the existing MAP workflows via routetask, then drives the selected chain (map-plan -> map-efficient -> map-check -> map-review, as routed) end-to-end to a committed feature branch in one session, auto-approving routine workflow-control holds and hard-stopping on…
map-resume
Resume an interrupted MAP workflow from .map/ /stepstate.json checkpoint. Use when returning after context exhaustion, /clear, or a session crash mid-workflow. Do NOT use to start new work; use map-plan or map-efficient.