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 diagrid-labs/dapr-skills --skill check-prereq-aspiregit clone --depth 1 https://github.com/diagrid-labs/dapr-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/diagrid-labs/dapr-skills/check-prereq-aspire)<a href="https://agentmods.dev/skills/diagrid-labs/dapr-skills/check-prereq-aspire"><img src="https://agentmods.dev/badge/skills/diagrid-labs/dapr-skills/check-prereq-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/diagrid-labs/dapr-skills/check-prereq-aspire"><img src="https://agentmods.dev/badge/skills/diagrid-labs/dapr-skills/check-prereq-aspire.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.00035 | $0.00810 |
| Opus 5.5 | $0.00014 | $0.00324 |
| Sonnet 5.5 | $0.00007 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade C, and why
check-prereq-aspire scanned grade C with 2 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 10d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- [Aspire CLI](https://aspire.dev/get-started/install-cli/) — install via `curl -sSL https://aspire.dev/install.sh | bash` or `irm https://aspire.dev/install.ps1 | iex` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [Aspire CLI](https://aspire.dev/get-started/install-cli/) — install via `curl -sSL https://aspire.dev/install.sh | bash` or `irm https://aspire.dev/install.ps1 | iex` This is a copy
86% identical to check-prereq-agent-dotnet — 36 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Prerequisites for Dapr Workflow .NET Aspire
Overview
This skill checks whether all prerequisites are installed for building Dapr Workflow applications with .NET Aspire. Run it only when you ask for it, for example before using the create-workflow-aspire skill. It is never run automatically as a pre-step.
Prerequisites
The following must be installed:
- .NET 10 SDK
- C# LSP Plugin
- Aspire CLI — install via
curl -sSL https://aspire.dev/install.sh | bashorirm https://aspire.dev/install.ps1 | iex - Docker or Podman
- Dapr CLI (version 1.18+)
Prerequisite Checks
Run ALL of these checks. Check steps 2-6 in parallel. Track which checks pass and which fail.
Step 1: Detect Operating System
Read the file at ../dapr-shared/prereq-detect-os.md and follow those instructions.
Step 2: Check the C# LSP plugin
Read the file at ../dapr-shared/prereq-check-csharp-lsp.md and follow those instructions.
Step 3: Check .NET SDK
Read the file at ../dapr-shared/prereq-check-dotnet-sdk.md and follow those instructions.
Step 4: Check Docker or Podman
Read the file at ../dapr-shared/prereq-check-docker-podman.md and follow those instructions.
Step 5: Check Dapr CLI
Read the file at ../dapr-shared/prereq-check-dapr-cli.md and follow those instructions.
Step 6: Check Aspire CLI
Read the file at ../dapr-shared/prereq-check-aspire-cli.md and follow those instructions.
Show final message
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.
- 10d ago Changed · +4 lines · -13 tokens per session 5e83e2763d70
- 15d ago Changed · +3 lines 93346afc2fa5
- 1mo ago First seen · 65 lines · 48 tokens per session scan C c90c9d44e321
check-prereq-aspire is a skill published in the GitHub repository diagrid-labs/dapr-skills (13 stars, last pushed 10d ago), licensed MIT. It adds 35 tokens to every session and 810 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It is 86% identical to check-prereq-agent-dotnet, differing in 36 lines, and is treated as a copy.
Other skills, from other repositories
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
<skill-name>
A template for defining a coding-agent skill, including its title, trigger situations, overview, workflow, common mistakes, and optional references.
ai-loop
Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.
spec-writing
A method for writing a software specification: a document that records decisions, reasons, boundaries, and ways to judge whether implementation succeeded. It first checks whether important unknowns require user clarification or technical research.
onboarding-unknown-codebase
A method for quickly understanding an unfamiliar codebase, meaning a software project whose structure and behavior you do not yet know. It builds a project map by examining overview files, directories, and one main execution path.
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.