Borrowing it
Nothing to install: this file belongs to nodealchemy/powernode-platform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nodealchemy/powernode-platform/develop/.claude/skills/deploy/SKILL.mdgit clone --depth 1 https://github.com/nodealchemy/powernode-platformWrote 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/nodealchemy/powernode-platform/deploy)<a href="https://agentmods.dev/skills/nodealchemy/powernode-platform/deploy"><img src="https://agentmods.dev/badge/skills/nodealchemy/powernode-platform/deploy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nodealchemy/powernode-platform/deploy"><img src="https://agentmods.dev/badge/skills/nodealchemy/powernode-platform/deploy.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00964 |
| Opus 5.5 | $0.00004 | $0.00386 |
| Sonnet 5.5 | $0.00002 | $0.00193 |
| Haiku 4.5 | $0.00001 | $0.00096 |
Grade D, and why
deploy scanned grade D with 3 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 1mo 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.
sudo systemctl restart "${UNIT:-powernode-worker@default}" 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.
curl -s http://localhost:3000/api/v1/health | python3 -m json.tool Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:3000/api/v1/health | python3 -m json.tool How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy — Local Service Restart & Verify
Safely restart local Powernode services and verify they're healthy. This is for LOCAL development restarts, not remote/Docker deployment.
Step 1: Pre-flight Check
pwd
git status --short | head -10
Note any uncommitted changes — warn if there are unstaged migrations.
Step 2: Restart Services
Based on scope (default: all):
backend
bash scripts/reload-backend.sh
Backend uses SIGUSR2 hot reload (~30ms). No downtime.
worker
This cell is module-composed: the unit is powernode-<moduleID>-sidekiq.service (a UUID),
never powernode-worker@default — a guessed name fails systemctl silently. Discover it,
then restart and verify the discovered unit (fall back to powernode-worker@default only if
discovery finds nothing, for a plain installer-shape host):
UNIT=$(systemctl list-units 'powernode-*-sidekiq.service' --no-pager --no-legend --plain | awk '{print $1}' | head -1)
sudo systemctl restart "${UNIT:-powernode-worker@default}"
systemctl is-active "${UNIT:-powernode-worker@default}"
Worker drains jobs before stopping (~28s), so the health check waits for it (Step 3).
worker-web (always restart with worker)
Same discovery, -worker-web instead of -sidekiq:
UNIT=$(systemctl list-units 'powernode-*-worker-web.service' --no-pager --no-legend --plain | awk '{print $1}' | head -1)
sudo systemctl restart "${UNIT:-powernode-worker-web@default}"
systemctl is-active "${UNIT:-powernode-worker-web@default}"
frontend
Same discovery, -frontend:
UNIT=$(systemctl list-units 'powernode-*-frontend.service' --no-pager --no-legend --plain | awk '{print $1}' | head -1)
sudo systemctl restart "${UNIT:-powernode-frontend@default}"
systemctl is-active "${UNIT:-powernode-frontend@default}"
all (default)
Restart in this order: backend (reload), worker + worker-web, frontend.
Step 3: Wait for Drain (worker only)
If worker was restarted, wait until its unit is active again before health checks (the ~30 s
drain). A foreground sleep is blocked in this harness, so wait with the Monitor tool running a
bounded until-loop on the discovered unit (shell state does not carry over, so discover it again):
UNIT=$(systemctl list-units 'powernode-*-sidekiq.service' --no-pager --no-legend --plain | awk '{print $1}' | head -1)
timeout 90 bash -c "until systemctl is-active --quiet '${UNIT:-powernode-worker@default}'; do sleep 2; done"
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.
- 1mo ago Changed · +3 lines 690f6a96e180
- 1mo ago Changed · +12 lines 785a9b03d359
- 2mo ago First seen · 93 lines · 11 tokens per session scan D 863acf8c6ba5
deploy is a skill published in the GitHub repository nodealchemy/powernode-platform (4 stars, last pushed 5d ago), licensed MIT. It adds 11 tokens to every session and 964 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it D with 3 findings (asks for root, 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-31.
Other skills, from other repositories
bi-clustering
A business-analysis skill that places similar business objects—such as users, products, or shops—into groups. It can use a two-by-two matrix based on two measures or clustering based on several features.
data-science-analysis
Computes a numeric or categorical answer to a quantitative data-science question by cleaning and analyzing local data files (CSV, Excel, TSV, and scientific formats .npz/.fits/.h5) with pandas, numpy, and scipy. Use whenever a task ships its own dataset (in whatever local directory it provides) and asks you to derive…
bi-attribution-analysis
A business-analysis skill that measures how much each group or dimension value contributed to a metric's change. It supports totals that can be added directly, rates such as conversion rate, and weighted averages such as average order value.
bi-conversion-analysis
A complete analysis of conversion: the percentage of people who move from a starting action, such as visiting, to a target action, such as registering, buying, or paying.
bi-retention-analysis
A workflow for measuring user retention, meaning how many users return or repeat a chosen activity after an initial event such as registration or first use.
bi-adaptive-threshold
A tool for calculating a change threshold from the natural variation in historical time-series data. A threshold is the boundary above which a change is treated as notable.