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/managedcode/dotnet-skills/aspirenpx skills add managedcode/dotnet-skills --skill aspiregit clone --depth 1 https://github.com/managedcode/dotnet-skillsWhat 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.00145 | $0.03041 |
| Opus 5 | $0.00072 | $0.01520 |
| Sonnet 5 | $0.00029 | $0.00608 |
| Haiku 4.5 | $0.00015 | $0.00304 |
Grade A, and why
aspire 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aspire
Trigger On
Aspire.AppHost.Sdk,Aspire.Hosting.*,DistributedApplication.CreateBuilder,apphost.mts,createBuilder,WithReference,WaitFor,AddProject,addNodeApp,addViteApp,AddRedis,AddPostgres,aspire run,aspire init,aspire add, oraspire updateAspire.Hosting.Testing,DistributedApplicationTestingBuilder, or a test harness that mixes an Aspire AppHost withWebApplicationFactory- orchestrating multiple services and resources with an AppHost for local development or cloud deployment
- setting up
ServiceDefaults, service discovery, OpenTelemetry, health checks, or the Aspire Dashboard - choosing between official first-party Aspire integrations and
CommunityToolkit/Aspire - upgrading older 8.x or 9.x Aspire solutions to the current CLI and AppHost SDK model
- wiring polyglot services into an Aspire topology, especially when Go, Bun, Java, Python, or extra dev-time tools enter the picture
Workflow
- Classify the task first: new AppHost creation, existing-solution enlistment, integration wiring, testing and observability, deployment, or version upgrade.
- Prefer the current Aspire toolchain. Choose a C# AppHost for .NET-first repositories or a TypeScript
apphost.mtsfor JavaScript/TypeScript-first repositories; both are first-class in 13.5. Use the Aspire CLI and current SDK-generated app model instead of writing new guidance around the deprecated legacy workload. - Treat 13.5.x releases as the current CLI-first app model. Keep the Aspire CLI,
Aspire.AppHost.Sdk, and closely coupled hosting or testing packages on the same line, then rerun the AppHost and deployment checks afteraspire update. - Keep the AppHost code-first and topology-focused. Model services, resources, dependencies, endpoints, lifetimes, and parameters there; keep business logic out.
- Keep
ServiceDefaultsnarrow. It exists for telemetry, health checks, resilience, and service discovery, not shared domain models or general utility code. - Prefer official first-party Aspire integrations when they cover the requirement. Use
CommunityToolkit/Aspireonly when the capability gap is real: unsupported language hosts, extra dev infrastructure, or extension packages the official project does not provide. - Validate the whole distributed system, not one project in isolation. Local success means the AppHost starts cleanly, dependencies resolve through
WithReference, the dashboard shows the expected resource graph, and end-to-end tests can exercise the topology. - For integration tests, keep one shared AppHost fixture per test session. Use
Aspire.Hosting.Testingto boot the distributed app, createHttpClientor SignalR clients from the AppHost, and layerWebApplicationFactoryon top only when tests need direct Host DI, grains, or runtime services. - When publishing, switch from local containers or emulators to managed resources deliberately and verify which services truly need external endpoints.
What ships with it
5 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.
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 · 122 lines · 145 tokens per session scan A 89292666c6b8
aspire is a skill published in the GitHub repository managedcode/dotnet-skills (477 stars, last pushed 2d ago), licensed MIT. It adds 145 tokens to every session and 3,041 once invoked, about $0.0007 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
winui-ui-testing
Automated UI testing for Windows desktop apps — generate a batch test script with the winapp ui UI Automation harness, run all tests in one pass, read results. Covers element assertions, interactions, value checking (TextBox, ComboBox, ToggleSwitch), keyboard shortcuts and typing (send-keys), hover, drag-and-drop…
pr-review
Multi-dimensional review of a PR or feature branch in microsoft/win-dev-skills. Activate on "review my PR / changes / branch", "vet before pushing", "PR review", "is this ready to merge". Fans out parallel sub-agents over skill content, the skill-vs-tool boundary (solution hierarchy), tool correctness…
winui-design
Use when designing, reviewing, or fixing WinUI 3: sample and control discovery with winapp find-ui, layout planning, control choice, Fluent Design alignment, Light/Dark/High Contrast theming, typography, spacing, brushes, accessibility, and XAML data-binding design. Load before authoring new XAML, reviewing UI PRs…
winui-dev-workflow
Build and run workflow for WinUI 3 apps with WinApp CLI 0.6+ — project creation with winapp new, project-mode winapp run, BuildAndRun.ps1 analyzer integration, crash diagnosis, and prerequisites. Use when creating, building, running, or fixing build errors in a WinUI 3 project.
winui-packaging
MSIX packaging, code signing, and distribution for WinUI 3 apps — build for release, certificate generation (winapp cert generate), certificate trust, code signing (winapp sign), self-contained deployment, CI/CD with GitHub Actions, and Microsoft Store submission. Use when preparing for release, creating MSIX…
winui-session-report
Analyze the current or a recent agent session (GitHub Copilot CLI or Claude Code) and generate a diagnostic report. Use only when the user explicitly asks for session feedback, agent debugging, or a review of what happened during a build session. Do not inspect session data automatically.