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 skills/erikdarlingdata/performancestudio/maintenancenpx skills add erikdarlingdata/PerformanceStudio --skill maintenancegit clone --depth 1 https://github.com/erikdarlingdata/PerformanceStudioWrote 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/erikdarlingdata/performancestudio/maintenance)<a href="https://agentmods.dev/skills/erikdarlingdata/performancestudio/maintenance"><img src="https://agentmods.dev/badge/skills/erikdarlingdata/performancestudio/maintenance.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.1 | $0.00031 | $0.02143 |
| Opus 5 | $0.00015 | $0.01071 |
| Sonnet 5 | $0.00006 | $0.00429 |
| Haiku 4.5 | $0.00003 | $0.00214 |
Grade A, and why
maintenance 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 yesterday.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Routine Maintenance Pass
A repeatable every-1-3-months health check for the .NET desktop + SQL-monitoring repos
(PerformanceMonitor = WPF, PerformanceStudio = Avalonia; same dependency/build/release shape).
$ARGUMENTS optionally scopes it (deps, build, or all — default all).
Work top to bottom. Do read-only scans first and report findings; make fixes on a feature
branch/worktree (branch protection: never commit to dev/main), build + test, then PR to dev.
Low-risk patch/minor bumps can go in one PR; majors and anything release-critical get their own.
A. Dependencies & Security
Scope — scan every project, not just the solution. A repo's
.slnmay not list every project. PerformanceStudio'sPlanViewer.slnomitsserver/PlanShare.csprojand the SSMS VSIX (PlanViewer.Ssms,PlanViewer.Ssms.Installer), so thedotnet list <Solution>.sln …scans and the solution build all silently skip them. Run the checks against those projects too. The net472 VSIX is old-style, sodotnet listis unreliable on it — read its<PackageReference>s by hand (itsMicrosoft.VSSDK.BuildToolsis intentionally held on the 17.x line; 18.x is un-restorable from nuget.org and targets VS 18, not VS 2022). Where the.slncovers all projects, the solution is enough.
- Outdated packages.
dotnet list <Solution>.sln package --outdated- Take low-risk patch/minor bumps (Microsoft.Extensions.*, Test.Sdk, etc.).
- Majors get their own effort — especially the update framework (Velopack: bump the library AND the
vpkCLI pin in the release workflow —.github/workflows/release.ymlfor PerformanceStudio — together; validate the in-app + Setup.exe update path) and anything release-critical. - Engine-wrapped bindings (e.g. DuckDB.NET) trail the native engine — bump when the binding catches up, and validate behavior (for DuckDB run
tools/CompactionReprore: the parquet-COPY memory-limit floor before changing the version). - After version edits, if the repo uses lock files (
packages.lock.json— PerformanceMonitor does; PerformanceStudio does not), regenerate them:dotnet restore <Solution>.sln --force-evaluate(CI restores--locked-mode).
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.
- yesterday First seen · 75 lines · 31 tokens per session scan A b9f08f042ec1
maintenance is a skill published in the GitHub repository erikdarlingdata/PerformanceStudio (236 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 2,143 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
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.
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…