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 commands/peterblazejewicz/claude-plugins/code-simplifygit clone --depth 1 https://github.com/peterblazejewicz/claude-pluginsWhat 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.00016 | $0.00525 |
| Opus 5 | $0.00008 | $0.00262 |
| Sonnet 5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
code-simplify 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 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.
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.
What it actually says
Invoke the dotnet-skills:code-simplification skill.
Simplify recently changed code (or the specified scope) while preserving exact behavior:
- Read
CLAUDE.mdand study project conventions —.editorconfig, analyzer severity, naming conventions, layering rules - Identify the target code — recent changes unless a broader scope is specified
- Understand the code's purpose, callers, edge cases, and test coverage before touching it
- Scan for C#-specific simplification opportunities:
- Deep nesting → guard clauses or extracted helpers
- Long methods → split by responsibility
- Nested ternaries →
switchexpressions or if/else - Generic names → descriptive names aligned with
.editorconfig - Manual null checks →
??,?., pattern-matching (is { } x), orArgumentNullException.ThrowIfNull async voidand sync-over-async → properTask/ValueTaskwithCancellationToken- Mutable DTOs →
record/record struct - Duplicated logic → shared methods, extension methods, or
requiredproperties - Dead code → remove after confirming with callers and tests
- Apply each simplification incrementally — run
dotnet testanddotnet build -warnaserrorafter each change - Verify all tests pass, the build succeeds warning-free,
dotnet format --verify-no-changesis clean, and the diff is tight
If tests fail after a simplification, revert that change and reconsider. Use dotnet-skills:code-review-and-quality to review the result.
Source & Modifications
- Upstream:
addyosmani/agent-skills—.claude/commands/code-simplify.mdat pinned SHA44dac80 - Status: modified (skill references retargeted to the
dotnet-skills:prefix; convention-sources list adds.editorconfig/ analyzer severity / layering rules; simplification scan gains C#-idiomatic opportunities — null-coalescing, pattern-matching,ArgumentNullException.ThrowIfNull, async correctness,record/record struct; verification commands aredotnet test,dotnet build -warnaserror,dotnet format --verify-no-changes)
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 · 33 lines · 16 tokens per session scan A 03b451058203
code-simplify is a command published in the GitHub repository peterblazejewicz/claude-plugins (7 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 525 once invoked, about $0.0001 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-31.
Other commands, from other repositories
orchestrator
You are Orchestrator, the autonomous operations manager for this project. You coordinate AI agent roles to execute tasks with minimal CEO involvement.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
update_docs
Use the text the user typed after the command name as the request for this command.
implement_feature
Use the text the user typed after the command name as the request for this command.
execute_plan
Use the text the user typed after the command name as the request for this command.
research
Use the text the user typed after the command name as the request for this command.