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 managedcode/dotnet-skills --skill aspiregit clone --depth 1 https://github.com/managedcode/dotnet-skillsWrote 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/managedcode/dotnet-skills/aspire)<a href="https://agentmods.dev/skills/managedcode/dotnet-skills/aspire"><img src="https://agentmods.dev/badge/skills/managedcode/dotnet-skills/aspire/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/managedcode/dotnet-skills/aspire"><img src="https://agentmods.dev/badge/skills/managedcode/dotnet-skills/aspire.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00145 | $0.03139 |
| Opus 5.5 | $0.00058 | $0.01256 |
| Sonnet 5.5 | $0.00029 | $0.00628 |
| Haiku 4.5 | $0.00015 | $0.00314 |
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 1mo 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 — 125 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. Fixture sharing amortizes startup and must not serialize tests; keep consumers parallel and isolate their mutable state. - 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.
- 1mo ago Changed · +2 lines 4fa4cefec5bf
- 1mo ago Changed · +1 lines 15bb010f802f
- 1mo ago First seen · 122 lines · 145 tokens per session scan A 89292666c6b8
aspire is a skill published in the GitHub repository managedcode/dotnet-skills (489 stars, last pushed today), licensed MIT. It adds 145 tokens to every session and 3,139 once invoked, about $0.0006 per session on Opus 5.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
sandbox-next
Build or maintain Cloudflare Sandbox apps on @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-migrate-to-next when porting a stable app.
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
cloudflare
Discover and choose Cloudflare products for apps, APIs, AI agents, storage, networking, and security. Use for architecture and product selection, including when the user describes a need without naming a Cloudflare product; then find the relevant skill or documentation.
airflow-state-store
Persists task and asset state across retries and DAG runs using Airflow 3.3's AIP-103 key/value stores (taskstatestore, assetstatestore) and the crash-safe ResumableJobMixin. Use when the user asks about task state store, checkpointing in tasks, persisting state across retries, job IDs surviving worker crashes…
generate-microcks-openapi-samples
Use when creating OpenAPI mock examples for Microcks, setting up request/response routing with dispatchers, or mapping request fields to mock responses.
aws-sdk-java-v2-messaging
Provides AWS messaging patterns using AWS SDK for Java 2.x for SQS queues and SNS topics. Handles sending/receiving messages, FIFO queues, DLQ, subscriptions, and pub/sub patterns. Use when implementing messaging with SQS or SNS.