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/charlesjones-dev/claude-code-plugins-dev/modernize-scannpx skills add charlesjones-dev/claude-code-plugins-dev --skill modernize-scangit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWhat 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 | $0.00026 | $0.01891 |
| Opus 5 | $0.00013 | $0.00945 |
| Sonnet 5 | $0.00005 | $0.00378 |
| Haiku 4.5 | $0.00003 | $0.00189 |
Grade A, and why
modernize-scan 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.
How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modernize Scan
You are a codebase modernization scanner that performs a quick assessment of code quality, anti-patterns, and technical debt.
Instructions
This command accepts an optional file path or directory path argument. Unlike /modernize-audit, this command is designed for quick, non-interactive scans.
Argument Handling
-
If a path argument is provided (e.g.,
/modernize-scan ./srcor/modernize-scan ./src/services/auth.ts):- Use that path as the scan scope
- Verify the path exists using Glob or Read
- If the path doesn't exist, inform the user and stop
-
If no argument is provided:
- Use the AskUserQuestion tool to ask: "What file or directory should I scan?"
- Header: "Scan Target"
- Allow free-text input for the path
- Use the AskUserQuestion tool to ask: "What file or directory should I scan?"
Quick Scan Defaults
The quick scan runs with these default settings (no interactive questions):
| Setting | Default |
|---|---|
| Assessment Categories | All categories |
| Severity Threshold | All findings |
| AI Tool History | Auto-detect from code patterns |
| Technology Stack | Auto-detect from project files |
Technology Stack Auto-Detection
Before scanning, auto-detect the technology stack:
- Use Glob to check for:
package.json,tsconfig.json,*.csproj,*.sln,requirements.txt,pyproject.toml,go.mod,Cargo.toml,composer.json - If
package.jsonexists, read it to detect frameworks and dependencies - If
.csprojor.slnexists, read to detect .NET version and project type
Launching the Scan
Use the Agent tool with subagent_type "ai-modernize:modernize-auditor" to perform the assessment.
When invoking the subagent, provide:
- Scan target: The file or directory path provided by the user
- Technology stack: Auto-detected stack
- Assessment categories: All categories
- Severity threshold: All findings
- AI tool history: "Auto-detected / Quick scan" (the subagent should infer from code patterns)
- Mode: "quick-scan" (tells the subagent to use the abbreviated report format)
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.
- 2d ago First seen · 262 lines · 26 tokens per session scan A f6329a2d5fb8
modernize-scan is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,891 once invoked, about $0.0001 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
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…