update-stack

A workflow for bringing changes from an upstream Devkit Node project into another Node.js project. Upstream means the original project that supplies the changes; the workflow first merges shared code and then adapts the receiving project.

In plain words
What is it for?
Use it to update a project from Devkit Node, synchronise its stack, or resolve conflicts during that update.
Why use it?
It separates copying shared updates from resolving project-specific differences. This makes it easier to keep local code aligned without accidentally changing upstream files.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/pierreb-devkit/node/update-stack
Any agent
npx skills add pierreb-devkit/Node --skill update-stack
Clone the repo
git clone --depth 1 https://github.com/pierreb-devkit/Node

Made for: Claude Code, Codex.

Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,544 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00099 $0.01544
Opus 5 $0.00049 $0.00772
Sonnet 5 $0.00020 $0.00309
Haiku 4.5 $0.00010 $0.00154

Measured yesterday against content hash 4e3dd302510e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update-stack 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 yesterday.

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.

.claude/skills/update-stack/SKILL.md · 142 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 142 lines · 99 tokens per session scan A 4e3dd302510e

Subscribe to this mod's changes

update-stack is a skill published in the GitHub repository pierreb-devkit/Node (20 stars, last pushed 4d ago), with no licence file. It adds 99 tokens to every session and 1,544 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-30.

Related

Other skills, from other repositories

push-to-forked-pr

Push the current working tree directly to a GitHub PR whose head lives on a fork, without creating a new branch and without pushing to origin (which is usually the upstream). Invoke when the user says things like "push straight to PR.

hoangsonww/Claude-Code-Agent-Monitor · 57 tokens

version-release

Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.

hoangsonww/Claude-Code-Agent-Monitor · 50 tokens

file-headers

MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start with the project's copyright/authorship header (file overview + exact author line). Use automatically whenever writing a new file or editing an existing one; do…

hoangsonww/Claude-Code-Agent-Monitor · 101 tokens

budget-set

Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a…

hoangsonww/Claude-Code-Agent-Monitor · 79 tokens

cache-efficiency

Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (totalcacheread / (totalcacheread + totalinput)), cachewrite vs cacheread reuse, cache-read vs cache-write spend, and the sessions with the poorest reuse. Pulls token totals from /api/analytics, per-session…

hoangsonww/Claude-Code-Agent-Monitor · 100 tokens

cost-breakdown

Break down Claude Code costs using the Agent Monitor pricing engine. Shows per-model costs (input, output, cacheread, cachewrite at $/Mtok rates), per-session costs, daily trends, and compaction baseline token recovery. Use when analyzing spending, comparing model costs, or planning budgets.

hoangsonww/Claude-Code-Agent-Monitor · 64 tokens