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 Christian-Katzmann/app-it --skill app-it-windowsgit clone --depth 1 https://github.com/Christian-Katzmann/app-itWrote 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/christian-katzmann/app-it/app-it-windows)<a href="https://agentmods.dev/skills/christian-katzmann/app-it/app-it-windows"><img src="https://agentmods.dev/badge/skills/christian-katzmann/app-it/app-it-windows/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/christian-katzmann/app-it/app-it-windows"><img src="https://agentmods.dev/badge/skills/christian-katzmann/app-it/app-it-windows.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.00089 | $0.01361 |
| Opus 5 | $0.00044 | $0.00681 |
| Sonnet 5 | $0.00018 | $0.00272 |
| Haiku 4.5 | $0.00009 | $0.00136 |
Grade A, and why
app-it-windows 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
app-it-windows - Make a project launchable on Windows (beta)
Windows beta: scaffolded, untested on real hardware, maintainer wanted.
The macOS app-it lane is proven. This Windows sibling mirrors the contract
with Windows primitives, but every runtime behavior that needs a real Windows
desktop must be marked deferred: this needs a Windows maintainer - see docs/WINDOWS.md.
Non-Negotiables
- Run
templates/inspect.ps1first and read the output before editing. - Trust disk over docs. Verify project type, scripts, ports, and desktop signals from files.
- Build everything a Mac or CI can build; never claim Windows runtime behavior works unless it was verified on real Windows hardware.
- Prefer the WPF + WebView2 host. Edge
--app=is a fallback, not the default. - Keep Windows visibly beta in every report and user-facing summary.
- Copy shipped templates and customize through
scripts\app-it.config.json. Do not re-derive launcher patterns. - Verify build/lint/config checks, then list hardware-only checks as deferred.
Reference Map
Open only what the inspection or chosen path needs:
references/maintainer-contract.md- what a Mac can produce, what must be deferred, and the exact Windows-maintainer phrase.references/inspection-and-strategies.md- project inspection, toolchain probes, strategy tree, W-Native, W-Edge, W-Static, W-Multi, B, and D.references/generated-files.md- template roster, allowed target files, config JSON, package scripts, and Start Menu destination.references/wrapper-host.md- WebView2 host, lifecycle, Job Object ownership, single-instance behavior, and wrapper argument contract.references/verification.md- buildable checks, Windows-only checks, and deferred rows.references/report-template.md- exact beta report format.
Templates
Templates live next to this file in templates/. Copy them into the target
project and keep their contracts intact:
templates/
wrapper-windows/
desktop-build.ps1
desktop-install.ps1
desktop-quit.ps1
inspect.ps1
run-template.ps1
run-template-edge.ps1
desktop-icons.ps1
placeholder-icon-gen.ps1
PSScriptAnalyzerSettings.psd1
app-it.config.example.json
What ships with it
26 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.
- references/generated-files.md 1.7 KB
- references/inspection-and-strategies.md 2.2 KB
- references/maintainer-contract.md 1.5 KB
- references/report-template.md 2.4 KB
- references/verification.md 1.0 KB
- references/wrapper-host.md 1.7 KB
- templates/app-it.config.example.json 3.5 KB
- templates/desktop-build.ps1 12 KB runs code
- templates/desktop-icons.ps1 8.6 KB runs code
- templates/desktop-install.ps1 5.2 KB runs code
- templates/desktop-quit.ps1 18 KB runs code
- templates/inspect.ps1 9.6 KB runs code
- templates/placeholder-icon-gen.ps1 11 KB runs code
- templates/PSScriptAnalyzerSettings.psd1 1000 B
- templates/run-template-edge.ps1 12 KB runs code
- templates/run-template.ps1 7.5 KB runs code
- templates/wrapper-windows/.gitignore 85 B
- templates/wrapper-windows/app.manifest 1.0 KB
- templates/wrapper-windows/App.xaml 670 B
- templates/wrapper-windows/App.xaml.cs 2.3 KB
- templates/wrapper-windows/DevServer.cs 7.6 KB
- templates/wrapper-windows/HostConfig.cs 5.0 KB
- templates/wrapper-windows/MainWindow.xaml 654 B
- templates/wrapper-windows/MainWindow.xaml.cs 11 KB
- templates/wrapper-windows/SingleInstanceGate.cs 3.1 KB
- templates/wrapper-windows/wrapper.csproj 3.7 KB
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.
- 9d ago First seen · 155 lines · 89 tokens per session scan A e8047e3a2e94
app-it-windows is a skill published in the GitHub repository Christian-Katzmann/app-it (217 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 1,361 once invoked, about $0.0004 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-30.
Other skills, from other repositories
claudexor
Use the local Claudexor control plane for harness-agnostic coding work across Claude Code, Codex, Cursor, and OpenCode. Use when a task benefits from route-aware harness and account selection, quota-aware account rotation, shared thread context, read-only planning or research, best-of-N execution, or cross-harness…
tfx-hub
A Korean-language skill for managing a TFX message hub, which is a local message bus for communication between coding agents. It supports starting, stopping, checking, and routing work through the hub.
tfx-plan
A workflow for breaking a coding task into an implementation plan. It reviews the proposed work using several planning and critique steps, with a quicker mode when needed.
tfx-review
A code-review workflow that asks several command-line AI reviewers to inspect changes independently, then reports issues that at least two reviewers agree on. TDD means test-driven development, where tests are written to guide implementation, but this add-on is for reviewing code rather than defining TDD.
merge-worktree
A Korean-language workflow for squash-merging a Git worktree branch into a target branch and creating a conventional commit message. A worktree is a separate working directory connected to the same Git repository; squash-merge combines its changes into one commit.
self-improve
The deliberate self-improvement loop for the maintainer — step back from fixing issues and improve Heimdall's OWN capability. Ports karpathy/autoresearch to Heimdall's routing/planning: collect evidence from metrics.jsonl + queue dead/done stats → form testable hypotheses → run a bounded routing experiment → evaluate…