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/trtmn/agent-plugins/skills-managernpx skills add trtmn/agent-plugins --skill skills-managergit clone --depth 1 https://github.com/trtmn/agent-pluginsWrote 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/trtmn/agent-plugins/skills-manager)<a href="https://agentmods.dev/skills/trtmn/agent-plugins/skills-manager"><img src="https://agentmods.dev/badge/skills/trtmn/agent-plugins/skills-manager.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 | $0.00103 | $0.00743 |
| Opus 5 | $0.00051 | $0.00371 |
| Sonnet 5 | $0.00021 | $0.00149 |
| Haiku 4.5 | $0.00010 | $0.00074 |
Grade A, and why
skills-manager 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 3d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills Manager
You manage skills using the npx skills CLI. Always use -y (yes flag) to skip interactive confirmation prompts so commands run non-interactively.
Commands
Find skills
npx skills find <query>
Returns a list of matching skills with install counts and URLs. Parse the output: skill identifiers look like owner/repo@skill-name.
Install a skill
# Global (user-level, available across all projects) — the default
npx skills add <owner/repo@skill> -g -y
# Project-level (only current directory)
npx skills add <owner/repo@skill> -y
# Install to a specific agent
npx skills add <owner/repo@skill> -g -a claude-code -y
# Install all skills from a repo
npx skills add <owner/repo> --all -g -y
List installed skills
npx skills list -g # global skills
npx skills list # project-level skills
npx skills list -g -a claude-code # filter by agent
Remove a skill
npx skills remove <skill-name> -g -y # global
npx skills remove <skill-name> -y # project
Check for updates
npx skills check
Update all skills
npx skills update
Typical workflows
User asks to find and install a skill:
- Run
npx skills find <relevant query> - Show the user the results (name, install count, URL)
- Ask which one they want, or if the best match is obvious, suggest it
- Install with
npx skills add <identifier> -g -y - Confirm what was installed and where
User asks to remove a skill:
- If they named it, run
npx skills remove <name> -g -y - If unsure of the exact name, first run
npx skills list -gto find it
User asks what skills they have:
Run npx skills list -g and present the results clearly.
User asks to update skills:
- Run
npx skills checkto show what's outdated - Run
npx skills updateto update everything, or ask if they want to be selective
Notes
- Default to global (
-g) install unless the user is clearly working on a project that should have its own skill set - The
findcommand output is non-interactive when a query argument is given — it prints results and exits - Skill identifiers use the format
owner/repo@skill-name(e.g.,vercel-labs/agent-skills@commit) - After installing a skill, it becomes available in the current session only after restarting Claude Code (let the user know)
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.
- 3d ago First seen · 82 lines · 103 tokens per session scan A 2cc229415464
skills-manager is a skill published in the GitHub repository trtmn/agent-plugins (2 stars, last pushed 7d ago), licensed Unlicense. It adds 103 tokens to every session and 743 once invoked, about $0.0005 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-31.
Other skills, from other repositories
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.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…