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/update-my-skillnpx skills add RongchangLi/pocketskill --skill update-my-skillgit clone --depth 1 https://github.com/RongchangLi/pocketskillWrote 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/rongchangli/pocketskill/update-my-skill)<a href="https://agentmods.dev/skills/rongchangli/pocketskill/update-my-skill"><img src="https://agentmods.dev/badge/skills/rongchangli/pocketskill/update-my-skill.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.00022 | $0.00751 |
| Opus 5 | $0.00011 | $0.00376 |
| Sonnet 5 | $0.00004 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
update-my-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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
When the user invokes this skill, update their Pocket Skill installation from origin/main, then refresh the my-skill plugin registration. If the user only wants to refresh local skill changes without pulling from remote, use refresh-my-skill instead.
Tool Expectations
This workflow may use git and shell commands.
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. Preflight
Before changing anything:
- Run
git rev-parse --is-inside-work-tree; if it fails, stop and explain that updates require a git checkout. - Run
git remote get-url origin; if it fails, stop and ask the user to add the Pocket Skill GitHub remote. - Run
git status --short; if there are uncommitted changes, stop and show the changed paths. Ask the user to commit, stash, or discard them before updating. Do not overwrite local skill edits. - Confirm
install.shexists and is executable. If it exists but is not executable, runchmod +x install.sh.
2. Pull From Main
Update from the remote main branch:
git fetch origin main- If not already on
main, switch withgit switch main git pull --ff-only origin main
If switching branches or pulling fails because of local changes, stop and report the blocker. Do not use git reset, forced checkout, or rebase unless the user explicitly asks.
3. Refresh My Skill Plugin
After the pull succeeds, refresh the plugin registration without bumping the version locally:
./install.sh --yes
This registers the marketplace and enables the my-skill plugin for detected tools:
- Claude Code:
/my-skill:<skill-name> - Codex:
$<skill-name> - General agents: direct
SKILL.mdfile usage
The refresh also exports categorized source directories (manage-skills/, my-skills/, private-skills/) into the flat skills/<name>/SKILL.md plugin cache required by Claude Code and Codex.
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.
- 5d ago First seen · 71 lines · 22 tokens per session scan A 49992efc15c7
update-my-skill is a skill published in the GitHub repository RongchangLi/pocketskill (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 751 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…