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/rongchangli/pocketskill/delete-skillnpx skills add RongchangLi/pocketskill --skill delete-skillgit clone --depth 1 https://github.com/RongchangLi/pocketskillWhat 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.00024 | $0.00675 |
| Opus 5 | $0.00012 | $0.00338 |
| Sonnet 5 | $0.00005 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
delete-skill 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
When the user invokes this skill, remove an existing Pocket Skill from their local library.
Tool Expectations
This workflow may use shell commands and git commands such as git rm.
All operations must happen from the pocketskill repository root. First locate it:
- Use the current working directory if it contains
plugins/my-skill/skills/andinstall.sh. - Otherwise search upward from the current working directory.
- If no root is found, ask the user for the pocketskill path and stop until they provide it.
Workflow
1. Identify The Target
- If the user did not name a skill, list directories under
plugins/my-skill/skills/my-skills/andplugins/my-skill/skills/private-skills/that containSKILL.md, then ask which one to remove. - Never list or offer skills from
plugins/my-skill/skills/manage-skills/. Built-in management skills cannot be deleted through this skill. - Skip
.DS_Store, cache files, and directories withoutSKILL.md. - If the user explicitly names a skill in
manage-skills/, refuse with the message "Built-in management skills cannot be deleted." - Confirm the target path is
<repo-root>/plugins/my-skill/skills/<parent-dir>/<skill-name>/where<parent-dir>ismy-skillsorprivate-skills. - If the target does not exist, stop.
2. Confirm Intent
Show the user:
- skill name
- absolute path
- whether it is public (
my-skills/) or private (private-skills/) - whether it appears tracked by git, if inside a git repository
Ask whether they want to:
- Delete it
- Archive it (move to
private-skills/)
Never remove a skill without explicit confirmation.
3. Delete Or Archive
For delete:
- If inside a git repository and the skill is tracked, use
git rm -r -- plugins/my-skill/skills/<parent-dir>/<skill-name>/. - Otherwise remove only the exact target directory after confirmation.
- Do not use broad globs.
For archive:
- If the skill is already in
private-skills/, tell the user it is already private. - Otherwise move the directory to
plugins/my-skill/skills/private-skills/<skill-name>/. - If that archive target already exists, ask for a different name.
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 · 84 lines · 24 tokens per session scan A 7d30043201aa
delete-skill is a skill published in the GitHub repository RongchangLi/pocketskill (2 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 675 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-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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.