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 cwoodruff/dotnet-claude-workshop-content --skill async-hygienegit clone --depth 1 https://github.com/cwoodruff/dotnet-claude-workshop-contentWrote 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/cwoodruff/dotnet-claude-workshop-content/async-hygiene)<a href="https://agentmods.dev/skills/cwoodruff/dotnet-claude-workshop-content/async-hygiene"><img src="https://agentmods.dev/badge/skills/cwoodruff/dotnet-claude-workshop-content/async-hygiene/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/cwoodruff/dotnet-claude-workshop-content/async-hygiene"><img src="https://agentmods.dev/badge/skills/cwoodruff/dotnet-claude-workshop-content/async-hygiene.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.00389 |
| Opus 5 | $0.00028 | $0.00195 |
| Sonnet 5 | $0.00011 | $0.00078 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
async-hygiene 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- async-hygiene — 100% identical, 0 lines differ
What it actually says
Async/Await Hygiene Sweep
Scan the target scope (default: whole solution) for each anti-pattern, in this order, and fix with the standard remedy:
| Anti-pattern | Find | Fix |
|---|---|---|
| Sync-over-async | .Result, .Wait(), .GetAwaiter().GetResult() |
Make the caller async and await |
async void |
any non-event-handler | Return Task |
| Missing CancellationToken | async public methods without a token parameter | Add CancellationToken cancellationToken = default and thread it through |
| Fire-and-forget | unawaited Task-returning calls | Await, or route through a background service with error handling |
Task.Run in ASP.NET request path |
Task.Run( in Api project |
Remove — the request is already on a thread-pool thread |
| Async lambda passed to sync delegate | async lambda to Action<> |
Change delegate type or restructure |
Unnecessary async/await wrapper |
method whose only await is the final return | Return the Task directly (unless in a using/try) |
| Blocking I/O in async method | File.ReadAllText, Thread.Sleep inside async |
Use async equivalents (ReadAllTextAsync, Task.Delay) |
Process: grep for each pattern → read the surrounding code (some hits are legitimate, e.g. Main, console tools) → fix true positives → dotnet build → report a table of what changed and any hits deliberately left alone with reasoning.
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.
- 9d ago First seen · 22 lines · 57 tokens per session scan A 80c2bc150c7a
async-hygiene is a skill published in the GitHub repository cwoodruff/dotnet-claude-workshop-content (2 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 389 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-31.
Other skills, from other repositories
dotnet-reverse
A guide for analyzing compiled .NET and C# programs, including managed Windows executables and libraries. Reverse engineering means studying compiled software to understand how it works, and decompiling turns it back into readable approximate source code.
check-bin-obj-clash
Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, or missing/overwritten…
build-perf-diagnostics
Diagnose MSBuild build performance bottlenecks using binary log analysis. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization…
dump-collect
Configure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps…
binlog-generation
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors…
binlog-failure-analysis
Analyze MSBuild binary logs to diagnose build failures. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating…