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/john-data-chen/hermes-agent-backup/package-upgradenpx skills add john-data-chen/hermes-agent-backup --skill package-upgradegit clone --depth 1 https://github.com/john-data-chen/hermes-agent-backupWrote 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/john-data-chen/hermes-agent-backup/package-upgrade)<a href="https://agentmods.dev/skills/john-data-chen/hermes-agent-backup/package-upgrade"><img src="https://agentmods.dev/badge/skills/john-data-chen/hermes-agent-backup/package-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.00028 | $0.01604 |
| Opus 5 | $0.00014 | $0.00802 |
| Sonnet 5 | $0.00006 | $0.00321 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
package-upgrade 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 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.
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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Package Upgrade Workflow
Batch-upgrade npm packages across multiple repos using pnpm.
Prerequisites
- All repos use pnpm as package manager
- GitHub CLI (
gh) or API access for opening PRs - Repos live under
~/projects/
Workflow (MANDATORY ORDER)
For each repo:
1. Prepare branch
cd ~/projects/<repo>
git checkout main
git pull
git checkout -b feat/john/update-packages-YYYYMMDD
If git checkout main fails due to uncommitted changes, stash first:
git stash
git checkout main
git pull
git checkout -b feat/john/update-packages-YYYYMMDD
Leave the stash on the old branch — the user can pop it when they return.
NEVER modify main directly. Always create a feature branch and open a PR.
2. Run upgrade
pnpm up -r --latest
If the upgrade fails (e.g. a package's latest version has a broken transitive dep), see the "Handling broken upstream deps" section in Pitfalls below.
3. Enforce version caps
After upgrade, check and revert these packages if they were bumped beyond the allowed range:
| Package | Cap | Where |
|---|---|---|
@types/node |
latest 24.x.x (e.g. ^24.13.2, not ^24.0.0) |
package.json or pnpm-workspace.yaml (catalog) |
@typescript/native-preview |
"beta" — do NOT upgrade |
package.json or pnpm-workspace.yaml (catalog) |
Revert with sed or manual edit, then confirm with grep.
4. Expo mobile (turborepo-starter-kit only)
For turborepo-starter-kit, the apps/mobile workspace uses Expo and requires a separate upgrade step:
pnpm mobile:expo:upgrade
Run this after the general pnpm up -r --latest and version cap enforcement, but before pnpm install.
5. Install
pnpm install
This regenerates the lockfile after any manual version reverts.
6. Verify
Run the project's verification suite to confirm nothing broke. Read the project's AGENTS.md for the exact commands; the standard set is:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 136 lines · 28 tokens per session scan A 1f232ef34ca8
package-upgrade is a skill published in the GitHub repository john-data-chen/hermes-agent-backup (2 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,604 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
rn-feature-development
This skill should be used when building any new feature in a React Native or Expo app, or when the /rn-dev-agent:rn-feature-dev command runs. Triggers on "build a feature", "add X to the app", "implement Y", "create a new screen", "rn-feature-dev", "feature development", "build me X", "add a screen", "wire up this…
using-rn-dev-agent
Entry point for the rn-dev-agent plugin. Maps user intent to the right command, agent, or skill. Use at the START of any React Native development conversation. Triggers on "I want to build", "build a feature", "add a feature to the app", "test this", "something is broken", "fix the crash", "help with my React Native…
rn-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — read project instructions and the declared package manager, inventory sessions/Metro/devices read-only, establish one exclusive simulator/emulator via typed session actions, apply and verify package integration and…
build-and-test
Explicit Codex workflow: Build the Expo/React Native app (local or EAS), install it, start Metro, then test a requested feature end-to-end.
check-env
Explicit Codex workflow: Check that the fenced React Native session, Metro, app target, and device inventory are ready for testing.
run-workflow
Explicit Codex workflow: Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.