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/thewolffish/wolffish-app/nodenpx skills add thewolffish/wolffish-app --skill nodegit clone --depth 1 https://github.com/thewolffish/wolffish-appWrote 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/thewolffish/wolffish-app/node)<a href="https://agentmods.dev/skills/thewolffish/wolffish-app/node"><img src="https://agentmods.dev/badge/skills/thewolffish/wolffish-app/node.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.00009 | $0.00825 |
| Opus 5 | $0.00005 | $0.00413 |
| Sonnet 5 | $0.00002 | $0.00165 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade B, and why
node scanned grade B with 1 finding 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 3d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Do NOT install Node yourself with raw `shell_exec` `sudo apt install nodejs` (or What it actually says
Node.js
Usage
Use node_check to verify a usable Node.js (24+) is available and get the version.
If not, call node_install (requires user approval) — and trust it.
node_install is the default and needs no admin rights: it reuses an existing
global Node ≥24 if one is present, and otherwise downloads the official no-root
Node into ~/.wolffish/bin. No package manager, no password prompt. This is the
same managed-first policy the python capability uses, so it works the same on a
fresh machine with nothing pre-installed.
node_install_system is optional and only for when the user explicitly wants
a globally visible Node in their own terminal. It installs system-wide via the OS
(Homebrew / official MSI+UAC / apt|dnf+sudo) and prompts once for the admin
password; if elevation is declined or unavailable, it falls back to the no-root
copy so the user is never left stuck. Prefer node_install unless asked otherwise.
Do NOT install Node yourself with raw shell_exec sudo apt install nodejs (or
pkexec/brew/winget/msiexec). Use the tools above — they route through the
shared password session and the approval gate. If one returns a permission or
"password prompt cancelled" error, surface it; that error is deterministic, so
don't retry the same command.
Once installed, use the shell_exec tool for node, npm, and npx commands.
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.
- 3d ago First seen · 118 lines · 9 tokens per session scan B ce527f0679e7
node is a skill published in the GitHub repository thewolffish/wolffish-app (5 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 825 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-computer-use
REQUIRED for any task that involves operating a desktop application — opening apps, clicking buttons, typing into fields, pressing keys, scrolling, dragging, reading what's on screen, moving or resizing windows, or verifying state after an action. Always use the agent-cu CLI commands (open, snapshot, click, type, key…
claude-api
Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports anthropic/@anthropic-ai/sdk; user asks for…
create-skill
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
gui-onboarding-verification-skill
GUI desktop app only. Launch two parallel Oz cloud agents with computer use to download and install the latest stable Linux Warp build, capture screenshots while walking through first-time onboarding in both logged-out and logged-in states, then selectively fan out follow-up cloud agents for distinct onboarding…
logging-and-error-reporting
How and when to log (log:: levels, safe macros) and report errors to Sentry (reporterror!) in the Warp codebase. Use when adding or reviewing any logging or error reporting — picking a log level, deciding log vs. reporterror!, keeping sensitive data out of logs, or surfacing an error to Sentry.
gui-integration-test
GUI desktop app only. Writes, runs, and debugs Warp integration tests using the custom Builder/TestStep framework in crates/integration. Use when adding a new integration test, fixing a failing integration test, wiring a test into the manual runner or nextest suite, or verifying end-to-end UI and terminal behavior in…