Borrowing it
Nothing to install: this file belongs to christian289/dotnet-with-claudecode. 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/christian289/dotnet-with-claudecode/main/.claude/skills/applying-wpf-dev-pack-feedback/SKILL.mdgit clone --depth 1 https://github.com/christian289/dotnet-with-claudecodeWrote 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/christian289/dotnet-with-claudecode/applying-wpf-dev-pack-feedback)<a href="https://agentmods.dev/skills/christian289/dotnet-with-claudecode/applying-wpf-dev-pack-feedback"><img src="https://agentmods.dev/badge/skills/christian289/dotnet-with-claudecode/applying-wpf-dev-pack-feedback.svg" alt="Measured on agentmods" 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.00088 | $0.02859 |
| Opus 5 | $0.00044 | $0.01430 |
| Sonnet 5 | $0.00018 | $0.00572 |
| Haiku 4.5 | $0.00009 | $0.00286 |
Grade A, and why
applying-wpf-dev-pack-feedback 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 8d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Applying wpf-dev-pack Feedback
This skill turns one feedback markdown file (produced by the
/wpf-dev-pack:collecting-wpf-dev-pack-feedback skill in a foreign WPF
session) into concrete changes inside the wpf-dev-pack plugin, then
records the application in FeedbackDocs/APPLIED-LOG.md and parks the
source document inside FeedbackDocs/.
It is the maintainer counterpart of the collecting skill.
When NOT to use this
- The feedback document has not been read manually yet — read it first.
- The working tree is not clean — apply the feedback against a known baseline so the resulting commit is reviewable.
$0was not provided — the skill needs exactly one argument: the path to the feedback markdown file (absolute, or relative to repo root).- More than one feedback document at a time — invoke the skill per file. Batch application is intentionally not supported.
Workflow
Copy this checklist and track progress:
Apply Progress:
- [ ] Step 1: Validate input and load the feedback md
- [ ] Step 2: Plan: review the summary, decide which items to apply
- [ ] Step 3: Apply each selected item (one at a time)
- [ ] Step 4: Flag whether a release is needed (NEVER bump the version here)
- [ ] Step 5: Move the md into FeedbackDocs/
- [ ] Step 6: Append a row to FeedbackDocs/APPLIED-LOG.md
- [ ] Step 7: Surface a commit message draft for the maintainer
Step 1 — Validate input and load
Treat $0 as the path to the feedback markdown file. Reject early if:
$0is empty or missing.- The file does not exist at the given path.
- The file name does not end with
-wpf-dev-pack-feedback.md. Legacy-wpf-devpack-feedback.mdis also accepted, for backwards compatibility with already-archived contributions.
Read the file. Identify:
- The H1 title line (one-line summary of the feedback).
- The
## 0. Summarytable (priority overview). - Each
## N.item with itsPhenomenon and causality,Proposal, andAdjacent skill boundaries / cross-linkssubsections.
What ships with it
1 file 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.
- 8d ago First seen · 249 lines · 88 tokens per session scan A 4db2d428a044
applying-wpf-dev-pack-feedback is a skill published in the GitHub repository christian289/dotnet-with-claudecode (41 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 2,859 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
reogrid
Use when embedding an Excel-like spreadsheet control in .NET WinForms/WPF applications — formula engine, cell editing, clipboard, undo/redo. ReoGrid: .NET spreadsheet component with NPOI-based Excel read/write.
managedcode-markitdown
Use ManagedCode.MarkItDown when a .NET application needs deterministic document-to-Markdown conversion for ingestion, indexing, summarization, or content-processing workflows. USE FOR: ManagedCode.MarkItDown integration; document ingestion flows; Office or rich-text conversion to Markdown; indexing and summarization…
lightningcad
Use when doing architectural facade panel layout and detailing in AutoCAD or ZWCAD — panel numbering, shop drawing generation, material optimization. LightningCAD: building envelope detailing plugin for AutoCAD/ZWCAD.
npoi
Use when reading/writing Excel (.xls/.xlsx) or Word (.doc/.docx) files in .NET without Microsoft Office — data import/export, report generation, template filling. NPOI: .NET port of Apache POI for Office file I/O in server environments.
mapsui
Use when embedding interactive 2D maps in .NET desktop (WinForms/WPF) or mobile (MAUI) applications — tile layers, vector features, map controls. Mapsui: cross-platform .NET map component library.
powerpoint-cli
PowerPoint CLI automation skill for Windows presentations. Use when a coding agent needs token-efficient, scriptable, or unattended PowerPoint automation via pptcli commands. Best for CI/CD, scheduled jobs, batch processing, PowerShell workflows, and bulk deck edits. Supports slides, shapes, text frames, tables…