Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add christian289/dotnet-with-claudecode/plugin install wpf-dev-packWrote 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/collecting-wpf-dev-pack-feedback)<a href="https://agentmods.dev/skills/christian289/dotnet-with-claudecode/collecting-wpf-dev-pack-feedback"><img src="https://agentmods.dev/badge/skills/christian289/dotnet-with-claudecode/collecting-wpf-dev-pack-feedback/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/christian289/dotnet-with-claudecode/collecting-wpf-dev-pack-feedback"><img src="https://agentmods.dev/badge/skills/christian289/dotnet-with-claudecode/collecting-wpf-dev-pack-feedback.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00118 | $0.02419 |
| Opus 5.5 | $0.00047 | $0.00968 |
| Sonnet 5.5 | $0.00024 | $0.00484 |
| Haiku 4.5 | $0.00012 | $0.00242 |
Grade A, and why
collecting-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 1mo 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Collecting wpf-dev-pack Feedback
This skill turns lessons learned in the current WPF session into a structured
improvement-feedback document for the wpf-dev-pack plugin. It does NOT modify
wpf-dev-pack and does NOT touch git — it only writes one markdown file to the
current working directory, which the user later contributes via pull request.
Why this exists
WPF work happens in projects OUTSIDE the dotnet-with-claudecode repository, and
that repo's local clone path differs per machine. Editing wpf-dev-pack from a
foreign session is infeasible, so improvements are captured as an accumulable md
and contributed separately (see the repo CONTRIBUTING guide).
Anonymity policy (MANDATORY)
The feedback document is a reusable artifact contributed across projects. It must describe the technical phenomenon and its causal chain only. The following content is PROHIBITED in any feedback document produced by this skill:
- Project, solution, repository, product, or codename
- Team, developer, or user name; email; account handle
- Date or time of when the issue was encountered
- Absolute or repo-relative file paths from the originating codebase
- Class, namespace, or member names that are unique to the originating project
(use generic placeholders such as
XxxView,XxxViewModel,XxxService) - Any other detail that can identify the originating project or person
Public framework / library / API names (e.g., HelixToolkit, ScottPlot,
CommunityToolkit.Mvvm, Prism, DispatcherPriority.ApplicationIdle) are
allowed because they are part of the technical context, not identifying
information.
Workflow
Copy this checklist and track progress:
Feedback Collection Progress:
- [ ] Step 1: Auto-draft feedback items from this session
- [ ] Step 2: Augment via interview (AskUserQuestion)
- [ ] Step 3: Sanitize and rewrite each item as a causal description
- [ ] Step 4: Write the md to the current directory
- [ ] Step 5: Audit the completed md for identifying information
- [ ] Step 6: Report path and contribution instructions
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.
- 1mo ago First seen · 234 lines · 118 tokens per session scan A 50537d4d1f96
collecting-wpf-dev-pack-feedback is a skill published in the GitHub repository christian289/dotnet-with-claudecode (41 stars, last pushed 2mo ago), licensed MIT. It adds 118 tokens to every session and 2,419 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
build-sample-matrix
Build the matrix of all the samples throughout different frameworks.
lightningcad
Use when doing architectural facade panel layout and detailing in AutoCAD, ZWCAD or GstarCAD — panel numbering, shop drawing generation, material optimization. LightningCAD: building envelope detailing plugin for AutoCAD/ZWCAD/GstarCAD.
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.
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.
onboarding
Walk a new developer through .NET project setup, architecture, key files, and first task. Use when someone new joins the team or needs to understand the codebase.
cratis-documentation-writing
Plan, write, and improve user-centered Cratis documentation with a clear reader journey and one primary Diátaxis purpose per page. Use for product docs, tutorials, how-to guides, reference, explanations, and documentation reviews. For executable examples use cratis-technical-examples; for release notes use…