Aspire Skills is a plugin and collection of instructions and extensions that help AI coding agents work with Aspire distributed applications. It guides agents through setting up, connecting, running, monitoring, and deploying these applications.
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 microsoft/aspire-skills --skill pr-reviewgit clone --depth 1 https://github.com/microsoft/aspire-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/microsoft/aspire-skills/pr-review)<a href="https://agentmods.dev/skills/microsoft/aspire-skills/pr-review"><img src="https://agentmods.dev/badge/skills/microsoft/aspire-skills/pr-review/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/microsoft/aspire-skills/pr-review"><img src="https://agentmods.dev/badge/skills/microsoft/aspire-skills/pr-review.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.00248 | $0.04579 |
| Opus 5.5 | $0.00099 | $0.01832 |
| Sonnet 5.5 | $0.00050 | $0.00916 |
| Haiku 4.5 | $0.00025 | $0.00458 |
Grade A, and why
pr-review scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **Safety-guardrail regression** — `dotnet run` → `aspire start`, `curl` → `aspire wait`, How it starts
The opening of the file, as written. The whole thing — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-review
Internal author skill. Lives under
.github/skills/so it is not part of the shipped Aspire plugin (whoseskillsglob is./skills/). Use this when reviewing PRs opened againstmicrosoft/aspire-skills.
You are a specialized PR review agent for the microsoft/aspire-skills repository. Your
goal is to identify problems only — bugs, regressions, missing or broken evals,
frontmatter or routing damage, plugin-manifest drift, unsafe hook commands, and
violations of repository conventions. Do not comment on style nits or add praise. Do
not suggest improvements that aren't fixing a problem.
When to activate
| Signal | Activate? |
|---|---|
| User says "review this PR", "review the current branch", or "check before merge" | ✅ Yes |
gh pr view / gh pr diff / GitHub PR URL referencing this repo in conversation |
✅ Yes |
Working tree is microsoft/aspire-skills and there is a non-empty diff vs main |
✅ Yes |
| User asks to review code in a consumer Aspire app | ❌ No — defer to the user's normal review flow |
User asks for runtime help with the aspire CLI |
❌ No — route to the shipped aspire skill |
CRITICAL: Step ordering
You MUST complete Step 1 (ensure the PR branch is available locally) BEFORE fetching
PR diffs or file lists. Branch-discovery calls (e.g., gh pr view <n> --json headRefName) are allowed, but do not call the diff or file-list APIs until Step 1 is
resolved. Skipping or reordering this step degrades review quality and violates the
skill workflow.
Understanding the user's request
Parse the user's request to extract:
- PR identifier — a PR number (e.g.,
5) or full URL (e.g.,https://github.com/microsoft/aspire-skills/pull/5). - Repository — defaults to
microsoft/aspire-skillsunless the user names a different repo. If the user names a different repo, stop and confirm they want this skill applied there — it is tuned for this repo's conventions.
What ships with it
4 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.
- 12d ago Changed · +8 lines fa3713b11957
- 13d ago Changed 58215ab4269c
- 1mo ago Changed fe1c8e4e976f
- 1mo ago Changed · +4 lines · +7 tokens per session c2288d8e3582
- 1mo ago Changed 11e522f69140
- 1mo ago First seen · 343 lines · 241 tokens per session scan A 78d4a2069bc9
pr-review is a skill published in the GitHub repository microsoft/aspire-skills (92 stars, last pushed yesterday), licensed MIT. It adds 248 tokens to every session and 4,579 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
meta-reviewing-ai-reviewing
AI integration review patterns. Use when reviewing model API calls, prompt construction, LLM output handling, RAG pipelines, and tool-calling code. Covers prompt-injection call-chain tracing, output validation, stop reasons, token budgets, retry and timeout handling, streaming, and key/PII exposure.
meta-reviewing-api-reviewing
Backend code review — injection and SSRF, boundary validation, object-level authorization, mass assignment and data exposure, error leakage, N+1 and unbounded queries. Use when a diff touches API routes or handlers, database access, auth middleware, or server code that reads files, starts processes or fetches URLs.
meta-reviewing-cli-reviewing
CLI code review — exit codes, cancellation and signals, non-TTY behaviour, the stdout/stderr split, error text, config precedence, subprocess safety and test adequacy. Load when reviewing a command-line tool's commands, entry point, prompts, output or tests, whichever parser or prompt library it uses.
meta-reviewing-infra-reviewing
Infrastructure code review — supply-chain pinning, secret exposure, workflow triggers and untrusted input, container hygiene, deployment safety. Load when reviewing a diff that touches CI/CD workflows, Dockerfiles, deployment configs or IaC.
meta-reviewing-web-reviewing
React component review — hook rules, effect cleanup, derived state, keys, memoization evidence and keyboard access. Load when reviewing a diff that adds or changes React components or hooks.
meta-reviewing-reviewing
Code review process — reading order, findings, severity, scope and the approval decision. Load when reviewing a diff or PR, writing review comments, or deciding whether to approve or request changes.