microsoft/wassette is a runtime that loads WebAssembly Components as tools exposed through the Model Context Protocol (MCP), an interface that lets AI agents use external capabilities. It is for extending coding agents with reusable tools while isolating those tools in a Wasmtime security sandbox. The catalogue skills, instructions, and agent help configure and operate Wassette with supported MCP clients.
Borrowing it
Nothing to install: this file belongs to microsoft/wassette. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/wassette/main/.agents/skills/pull-request/SKILL.mdgit clone --depth 1 https://github.com/microsoft/wassetteWrote 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/wassette/pull-request)<a href="https://agentmods.dev/skills/microsoft/wassette/pull-request"><img src="https://agentmods.dev/badge/skills/microsoft/wassette/pull-request/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/wassette/pull-request"><img src="https://agentmods.dev/badge/skills/microsoft/wassette/pull-request.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.00051 | $0.00289 |
| Opus 5.5 | $0.00020 | $0.00116 |
| Sonnet 5.5 | $0.00010 | $0.00058 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
pull-request 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 2mo 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.
What it actually says
pull-request skill
Keep Wassette pull request descriptions concise and focused.
Rules
- Describe the change in at most three sentences.
- Focus on the what and why, not implementation details.
- If the PR breaks a public-facing API, use one or two sentences to state what breaks and how users should adapt.
Example
This PR adds instrumentation to the MCP server runtime. It enables performance
monitoring and debugging of tool execution. The changes are backward compatible
with existing configurations.
Breaking-change example
This PR refactors the component registry API to support versioning. The
ComponentRegistry::register() method now requires a version parameter. Existing
code should pass a version string as the second argument.
Before opening
- Use a clear, user-facing title because GitHub generates release notes from merged pull request titles.
- Most contributions require a Contributor License Agreement; the CLA bot will
tell you if one is needed. See
CONTRIBUTING.md.
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.
- 2mo ago First seen · 40 lines · 51 tokens per session scan A d6fc3822e49e
pull-request is a skill published in the GitHub repository microsoft/wassette (972 stars, last pushed 3d ago), licensed MIT. It adds 51 tokens to every session and 289 once invoked, about $0.0002 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
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
git-workflow
Follow this team's Git conventions for branching, commit messages, and pull requests.
git-workflow
Git best practices for version control and collaboration.
p4-stream-workflows
P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools. Use when: creating streams, branching, merging, copying between streams, integrating changes, switching workspaces, or managing stream specs in P4.
p4-workspace-setup
P4 workspace setup and management — create, configure, sync, and switch workspaces via P4 MCP tools. Use when: creating workspaces, configuring client specs, syncing files, switching workspaces, or checking workspace status in P4.
issue-management
Create, update, list and search GitHub issues and PRs, list a repository's labels, run milestones, and check for duplicates.