PerformanceMonitor: Skill for Claude Code

.claude/skills/maintenance/SKILL.md

maintenance is a skill for Claude Code from erikdarlingdata/PerformanceMonitor. It costs 31 tokens per session (2,143 once invoked), scanned A, original, MIT.

A recurring maintenance workflow for .NET desktop and SQL-monitoring repositories. It checks dependencies, security, builds, tests, and repository cleanliness.

In plain words
What is it for?
Use it for dependency and security audits, build-health checks, repository-wide project scans, and maintenance fixes prepared for a pull request.
Why use it?
It helps uncover outdated or vulnerable packages and build problems that may be missed when only the main solution is checked. It also keeps changes on a separate branch before review.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

This is erikdarlingdata/PerformanceMonitor's own configuration. It tells Claude Code how to work on PerformanceMonitor itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything PerformanceMonitor configures →

Reuse

Borrowing it

Nothing to install: this file belongs to erikdarlingdata/PerformanceMonitor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/erikdarlingdata/PerformanceMonitor/main/.claude/skills/maintenance/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/erikdarlingdata/PerformanceMonitor

Made for: Claude Code.

Wrote 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.

agentmods badge for maintenance

README.md
[![agentmods](https://agentmods.dev/badge/skills/erikdarlingdata/performancemonitor/maintenance/github.svg)](https://agentmods.dev/skills/erikdarlingdata/performancemonitor/maintenance)
Your own site
<a href="https://agentmods.dev/skills/erikdarlingdata/performancemonitor/maintenance"><img src="https://agentmods.dev/badge/skills/erikdarlingdata/performancemonitor/maintenance/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.

agentmods 80×15 button for maintenance

Your own site · 80×15
<a href="https://agentmods.dev/skills/erikdarlingdata/performancemonitor/maintenance"><img src="https://agentmods.dev/badge/skills/erikdarlingdata/performancemonitor/maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,143 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash b9f08f042ec1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-13, from the pricing page.

Security

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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/maintenance/SKILL.md · 75 lines

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 .sln may not list every project. PerformanceStudio's PlanViewer.sln omits server/PlanShare.csproj and the SSMS VSIX (PlanViewer.Ssms, PlanViewer.Ssms.Installer), so the dotnet 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, so dotnet list is unreliable on it — read its <PackageReference>s by hand (its Microsoft.VSSDK.BuildTools is intentionally held on the 17.x line; 18.x is un-restorable from nuget.org and targets VS 18, not VS 2022). Where the .sln covers all projects, the solution is enough.

  1. 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 vpk CLI pin in the release workflow — .github/workflows/release.yml for 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/CompactionRepro re: 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).

Read the full file on GitHub · 75 lines

Changes

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.

  1. 2d ago First seen · 75 lines · 31 tokens per session scan A b9f08f042ec1

Subscribe to this mod's changes

maintenance is a skill published in the GitHub repository erikdarlingdata/PerformanceMonitor (494 stars, last pushed today), 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-10.

Related

Other skills, from other repositories

hithink-finance

A routing guide for accessing Chinese A-share financial data, including prices, company reports, valuations, funds, indices, sectors, and local data storage.

HiThink-Tech/Financial-API · 93 tokens

hithink-finance-data

A local data-management skill for the HiThink Finance command-line tool and its DuckDB database. DuckDB is a database stored in a local file.

HiThink-Tech/Financial-API · 60 tokens

hithink-finance-special-data

A command-line tool entry for retrieving special Chinese market lists and event data, such as limit-up stocks, limit-down stocks, unusual moves, hot stocks, and Dragon-Tiger records.

HiThink-Tech/Financial-API · 82 tokens

hithink-finance-futures

A command-line data source for public futures-market information, including contracts, positions, warehouse receipts, basis, trading schedules, and price charts. Futures are agreements to buy or sell an asset at a set future date.

HiThink-Tech/Financial-API · 78 tokens

hithink-finance-index

A command-line tool entry for finding Chinese indices, their categories, constituent stocks, current snapshots, and daily history. An index is a group of securities tracked as one measure, such as an industry or market segment.

HiThink-Tech/Financial-API · 68 tokens

hithink-finance-research

A workflow guide for preparing neutral, reproducible research data from Chinese market data. Reproducible means another person can repeat the same steps and obtain comparable results.

HiThink-Tech/Financial-API · 69 tokens