win-setup

win-setup is a skill for Claude Code, Codex from The-Biomechanist/Windows-Dev-Agent. It costs 28 tokens per session (467 once invoked), scanned A, original, MIT.

A procedure for setting up or repairing a Windows development environment, including runtimes, command-line tools, package managers, and native Windows settings.

In plain words
What is it for?
Use it to inspect Windows prerequisites, repair the earliest missing dependency, install a verified system package, or enable a required Windows feature.
Why use it?
It helps identify whether a problem comes from a missing tool, a broken configuration, PATH changes, an incompatible version, or a project dependency before making repairs.

Skill for Claude CodeCodex

Part of the windows-dev-agent plugin — 6 skills, 3 commands, 1 agent, 4 hooks, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add skills/the-biomechanist/windows-dev-agent/win-setup
Any agent
npx skills add The-Biomechanist/Windows-Dev-Agent --skill win-setup
Clone the repo
git clone --depth 1 https://github.com/The-Biomechanist/Windows-Dev-Agent

Made for: Claude Code, Codex.

Or install windows-dev-agent, the plugin that ships this one along with the rest of its 6 skills, 3 commands, 1 agent, 4 hooks, 1 MCP server.

Wrote 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.

agentmods badge for win-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/the-biomechanist/windows-dev-agent/win-setup.svg)](https://agentmods.dev/skills/the-biomechanist/windows-dev-agent/win-setup)
Your own site
<a href="https://agentmods.dev/skills/the-biomechanist/windows-dev-agent/win-setup"><img src="https://agentmods.dev/badge/skills/the-biomechanist/windows-dev-agent/win-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 467 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00028 $0.00467
Opus 5 $0.00014 $0.00234
Sonnet 5 $0.00006 $0.00093
Haiku 4.5 $0.00003 $0.00047

Measured 4d ago against content hash a79e18f93b3b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

win-setup 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 4d 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.

skills/win-setup/SKILL.md · 25 lines

How it starts

The opening of the file, as written. The whole thing — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Windows Setup

Procedure

  1. Inspect current state first. Use env_inspect and project requirements. Preserve null/unknown probe state; do not reinstall a tool merely because discovery failed to establish it.
  2. Locate the earliest missing or broken prerequisite. Distinguish runtime absence, unknown probe state, PATH/session propagation, version mismatch, package-manager failure, project dependency failure, and Windows feature state.
  3. Choose the native repair. Prefer the smallest Windows-owned change that repairs that prerequisite. Do not turn a local project problem into a machine-wide setup rewrite.
  4. For system packages, resolve identity before install. Preserve an exact ID supplied by the user or authoritative project/config state. Otherwise call package_search, inspect the candidates, and call package_install with execute: false for the resolved ID before requesting execution.
  5. For Windows optional features, use an explicitly approved PowerShell action only when the feature is actually required. WSL, Windows Sandbox, and Hyper-V are OS features, not ordinary package installs. If feature discovery is unknown because the current process could not establish it, resolve that fact before treating the feature as absent.
  6. For project dependencies, switch to the project's own package manager only after the required runtime/toolchain is established. Preserve lockfiles and project conventions. Project-code/build/test execution follows the active host's ordinary permission path.
  7. Verify the repaired joint with fresh state. Prefer the narrow version, availability, build, or project check that can establish the requested post-state. If full env_inspect is the right witness after a host mutation, use force_refresh: true.

Rules

  • Never use --silent to bypass license or installer interaction.
  • Resolve an exact package identity before installation; do not guess WinGet IDs.
  • Do not treat a successful installer exit as proof that the current shell sees the new PATH.
  • Do not mutate unrelated runtimes or package-manager state while repairing one dependency.
  • If elevation or restart is required, state that post-state explicitly rather than claiming completion early.

Read the full file on GitHub · 25 lines

Changes

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.

  1. 4d ago First seen · 25 lines · 28 tokens per session scan A a79e18f93b3b

Subscribe to this mod's changes

win-setup is a skill published in the GitHub repository The-Biomechanist/Windows-Dev-Agent (0 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 467 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

cost-efficiency-analyzer

Analyzes cost structure, cost efficiency, and expense management from P&L data. Use when the user asks about costs, expenses, COGS, operating expenses, cost ratios, cost control, spending efficiency, margin compression from cost side, or wants to understand where money is going. Also use for "are we spending too…

awslabs/agentcore-samples · 98 tokens

executive-financial-briefing

Generates a concise executive-level financial briefing or summary suitable for a CEO, CFO, or board presentation. Use when the user asks for a summary, briefing, executive summary, board update, financial overview, financial health check, or "how is the business doing". Covers the full P&L picture in one page. Also…

awslabs/agentcore-samples · 95 tokens

multi-quarter-trend-analysis

Analyzes financial trends across multiple quarters by comparing P&L metrics over time. Use when the user wants to see trends, patterns, trajectories, or directional movement across 3 or more quarters. Also use for "how are we trending", "show me the trend", "track performance over time", "quarter over quarter…

awslabs/agentcore-samples · 82 tokens

quarterly-kpi-calculator

Calculates quarterly financial KPIs from P&L data. P&L figures can be provided directly by the user or fetched from the financial data MCP server. Use when the user wants KPI calculations such as Gross Margin %, EBITDA Margin %, Operating Expense Ratio, or Revenue Growth % QoQ. Also use for quarterly performance…

awslabs/agentcore-samples · 84 tokens

babysit

Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…

kirodotdev/KiroCrew · 137 tokens

kirocrew-app-dev

Build, package, and publish KiroCrew external apps. Covers app.json manifest, UI components, crons, skills, self-healing install, git publishing, and common pitfalls.

kirodotdev/KiroCrew · 43 tokens