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 agentmods add instructions/notmyself/new-windows-dev-pc/claude-mdgit clone --depth 1 https://github.com/NotMyself/new-windows-dev-pcWrote 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/instructions/notmyself/new-windows-dev-pc/claude-md)<a href="https://agentmods.dev/instructions/notmyself/new-windows-dev-pc/claude-md"><img src="https://agentmods.dev/badge/instructions/notmyself/new-windows-dev-pc/claude-md.svg" alt="Measured on agentmods" 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 | $0.01262 | $0.01262 |
| Opus 5 | $0.00631 | $0.00631 |
| Sonnet 5 | $0.00252 | $0.00252 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade B, and why
new-windows-dev-pc CLAUDE.md scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Claude Code settings: `settings/claude/settings.json` → `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repository Purpose
This is a Windows developer setup automation repository containing PowerShell scripts to install and configure development tools, IDEs, and environments for new developers.
Key Commands
Main Setup Commands
.\install.ps1- Main installation script with PowerShell 7+ detection and WSL setup- Requires Administrator privileges (automatically elevates with proper error handling)
- Optional parameters:
-SkipWinGet,-SkipNpmPackages,-SkipExtensions - Installs 30+ development tools via WinGet package manager
- Always installs and configures WSL (Ubuntu-22.04) with development environment
- Installs Cascadia Code fonts with registry integration from
fonts/CascadiaCode.zip - Installs global npm packages and 38+ VSCode extensions
pwsh .\configure.ps1- Interactive configuration wizard for complete development environment setup- Requires PowerShell 7+ (displays clear upgrade instructions if older version detected)
- Always configures Claude Code for WSL with bash shell and formatting tools
- Interactive mode: Step-by-step configuration with explanations and user confirmations
- Fast mode: Use
-SkipConfirmationto bypass all prompts for automated deployment - Force mode: Use
-Forceto overwrite existing configurations - Windows 11 optimizations: Opt-in enhanced features during configuration
- Developer Mode detection: Uses symbolic links without Administrator privileges when enabled
Component Scripts
.\installs\winget.ps1- Installs development tools via WinGet package manager.\installs\vscode.ps1- Installs VSCode extensions from the extensions list.\installs\install-winget.ps1- Installs WinGet if not present
Administrative Requirements
All main scripts require Administrator privileges and will check for elevation before running.
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.
- 4d ago First seen · 103 lines · 1,262 tokens per session scan B 2c8f9db9d2c0
new-windows-dev-pc CLAUDE.md is an instructions file published in the GitHub repository NotMyself/new-windows-dev-pc (24 stars, last pushed 12mo ago), licensed MIT. It adds 1,262 tokens to every session, about $0.0063 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
maui uitests.instructions.md
Instructions for dotnet/maui, covering ui testing guidelines for .net maui, ui test structure, two-project requirement, base class and infrastructure and naming conventions.
maui performance-hotpaths.instructions.md
Instructions for dotnet/maui, covering performance-critical path rules, hot paths in maui, allocation avoidance, caching and invalidation and collection iteration.
maui collectionview-windows.instructions.md
Instructions for dotnet/maui, covering collectionview — windows (items/ handler), winui listview/itemsrepeater patterns, data source and change notifications, layout configuration and cross-platform consistency.
codex-provider-sync AGENTS.md
Instructions for Dailin521/codex-provider-sync, covering ai / agent operator guide, vnext architecture baseline, goal, choose the interface and safe operating flow.
Grace AGENTS.md
AGENTS.md instructions for ScottArbeit/Grace, covering agent instructions, agent quickstart (local), issue tracking, development process and markdown guidelines.
mcp-dotnet-samples AGENTS.md
AGENTS.md instructions for microsoft/mcp-dotnet-samples, covering agents.md - mcp .net samples, project overview, project structure and architecture, repository organization and sample components.