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/nmrtn/nanopm/pm-upgradenpx skills add nmrtn/nanopm --skill pm-upgradegit clone --depth 1 https://github.com/nmrtn/nanopmWrote 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/nmrtn/nanopm/pm-upgrade)<a href="https://agentmods.dev/skills/nmrtn/nanopm/pm-upgrade"><img src="https://agentmods.dev/badge/skills/nmrtn/nanopm/pm-upgrade.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.00042 | $0.01654 |
| Opus 5 | $0.00021 | $0.00827 |
| Sonnet 5 | $0.00008 | $0.00331 |
| Haiku 4.5 | $0.00004 | $0.00165 |
Grade C, and why
pm-upgrade scanned grade C with 2 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 4d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
{ echo "ERROR: nanopm not installed. Run: curl -fsSL https://raw.githubusercontent.com/nmrtn/nanopm/main/setup | bash"; exit 1; } Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
{ echo "ERROR: nanopm not installed. Run: curl -fsSL https://raw.githubusercontent.com/nmrtn/nanopm/main/setup | bash"; exit 1; } How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-host portability rules. When invoking
AskUserQuestion:
- The
headerfield MUST be a short noun phrase (≤ 12 characters). Mistral Vibe rejects longer headers withstring_too_long. Pick from:Start,Target,Scope,Audience,Methodology,Feature,Question.- The
optionslist MUST have at least 2 items. Vibe rejects empty/single-option calls. For free-text input, always provide ≥ 2 framing options (e.g.Yes, here's the input/Skip) — never callask_user_questionwithoptions: [].
Preamble (run first)
source ~/.nanopm/lib/nanopm.sh 2>/dev/null || \
source .nanopm/lib/nanopm.sh 2>/dev/null || \
{ echo "ERROR: nanopm not installed. Run: curl -fsSL https://raw.githubusercontent.com/nmrtn/nanopm/main/setup | bash"; exit 1; }
nanopm_preamble
Inline upgrade flow
This section is followed by all skill preambles when they detect UPGRADE_AVAILABLE {old} {new} in the preamble output.
Step 1: Ask or auto-upgrade
Check if auto-upgrade is configured:
source ~/.nanopm/lib/nanopm.sh 2>/dev/null || source .nanopm/lib/nanopm.sh 2>/dev/null || true
_AUTO=$(nanopm_config_get "auto_upgrade")
echo "AUTO_UPGRADE=${_AUTO:-false}"
If AUTO_UPGRADE=true: skip AskUserQuestion. Log "Auto-upgrading nanopm v{old} → v{new}..." and proceed to Step 2.
Otherwise, ask via AskUserQuestion:
- Question: "nanopm v{new} is available (you have v{old}). Upgrade now?"
- Options:
- "Yes, upgrade now"
- "Always keep me up to date (auto-upgrade)"
- "Not now (remind me later)"
- "Never ask again"
If "Yes, upgrade now": proceed to Step 2.
If "Always keep me up to date":
source ~/.nanopm/lib/nanopm.sh 2>/dev/null || source .nanopm/lib/nanopm.sh 2>/dev/null || true
nanopm_config_set "auto_upgrade" "true"
Tell user: "Auto-upgrade enabled — future updates will install automatically." Then proceed to Step 2.
If "Not now": write snooze state with escalating backoff. Then continue with the originally invoked skill without upgrading.
_SNOOZE="$HOME/.nanopm/update-snoozed"
_REMOTE_VER="{new}"
_CUR_LEVEL=0
if [ -f "$_SNOOZE" ]; then
_SV=$(awk '{print $1}' "$_SNOOZE")
if [ "$_SV" = "$_REMOTE_VER" ]; then
_CUR_LEVEL=$(awk '{print $2}' "$_SNOOZE")
case "$_CUR_LEVEL" in *[!0-9]*) _CUR_LEVEL=0 ;; esac
fi
fi
_NEW_LEVEL=$(( _CUR_LEVEL + 1 ))
[ "$_NEW_LEVEL" -gt 3 ] && _NEW_LEVEL=3
echo "$_REMOTE_VER $_NEW_LEVEL $(date +%s)" > "$_SNOOZE"
Tell user the snooze duration: level 1 → "next reminder in 24h"; level 2 → "48h"; level 3 → "1 week".
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.
- 4d ago First seen · 174 lines · 42 tokens per session scan C 8b692c13347c
pm-upgrade is a skill published in the GitHub repository nmrtn/nanopm (48 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,654 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…