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/andresharpe/dotbot/tech-preflight-dotnetnpx skills add andresharpe/dotbot --skill tech-preflight-dotnetgit clone --depth 1 https://github.com/andresharpe/dotbotWrote 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/andresharpe/dotbot/tech-preflight-dotnet)<a href="https://agentmods.dev/skills/andresharpe/dotbot/tech-preflight-dotnet"><img src="https://agentmods.dev/badge/skills/andresharpe/dotbot/tech-preflight-dotnet.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 | $0.00052 | $0.00551 |
| Opus 5 | $0.00026 | $0.00275 |
| Sonnet 5 | $0.00010 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
tech-preflight-dotnet 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 4d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Environment Pre-flight
Validate the local .NET environment against the solution's requirements before any code changes begin.
Workflow
- Check SDK/runtime compatibility — run
dotnet --list-sdks, compare against<TargetFramework>and<TargetFrameworks>(plural, for multi-targeting) in all.csprojfiles, flag gaps - Map the dependency graph — run
dotnet list {solution}.sln reference, identify layering violations - Run baseline build — run
dotnet build {solution}.sln, record error/warning counts for later comparison
1. SDK/Runtime Compatibility
dotnet --list-sdks
# Compare output against <TargetFramework> and <TargetFrameworks> values in *.csproj
- Flag any target framework without a matching SDK (e.g.,
net7.0targeted but onlynet8.0installed) - Note whether rollforward is viable (works for minor version gaps)
- Record in
environment.sdk_gaps
2. Project Dependency Graph
dotnet list {solution}.sln reference
For each project in the output:
- Map which projects reference which
- Identify layering patterns (e.g.,
.Interfaces→.Coreis OK,.Interfaces→.Entitiesmay not be) - Record in
environment.dependency_graph
Architecture enforcement — when placing new types:
- Do NOT add references that violate the existing dependency direction
- If a new type references entities from project B, it must live in a project that already references B
- Include any required
<ProjectReference>additions in implementation guidance - Flag circular dependencies immediately
3. Baseline Build
dotnet build {solution}.sln
- Record error count, warning count, and specific error messages
- Record in
environment.baseline_build - The execution phase compares against this to distinguish new vs pre-existing failures
Checklist
- All target frameworks have matching SDKs (or viable rollforward)
- Dependency graph has no circular references
- Baseline build output captured for comparison
- Any SDK gaps or layering issues flagged before code changes begin
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.
- 4d ago First seen · 62 lines · 52 tokens per session scan A 3aa084442e8e
tech-preflight-dotnet is a skill published in the GitHub repository andresharpe/dotbot (54 stars, last pushed 7d ago), licensed MIT. It adds 52 tokens to every session and 551 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
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
video-perception
Use when the user mentions a video file (.mp4, .mov, .avi, .mkv, .webm), a YouTube URL, asks to watch/analyze/review a video, or references video content in conversation.
csharp-dotnet
Use when writing, reviewing, testing, or shipping C# / .NET code — ASP.NET Core APIs (minimal APIs vs controllers), EF Core data access, async correctness, solution layout in .cs/.csproj/.sln. NOT a Java/Spring backend (that is spring-boot), NOT a Node/TypeScript backend (that is nestjs), NOT framework-neutral REST…
tsa-edit-then-verify
The full edit-and-verify loop mandated by CLAUDE.md and docs/agent-tooling-gap-report.md:58. Pre-edit gate (edit action=safe + baseline health action=file) → LLM edits → post-edit verify (health action=file diff + edit action=impact + scoped verificationcommand). Replaces "edit then run the whole pytest suite" (5 min)…