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/nodealchemy/powernode-platform/deploynpx skills add nodealchemy/powernode-platform --skill deploygit clone --depth 1 https://github.com/nodealchemy/powernode-platformWhat 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.00011 | $0.00576 |
| Opus 5 | $0.00005 | $0.00288 |
| Sonnet 5 | $0.00002 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00058 |
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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo systemctl restart 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 What it actually says
/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
sudo systemctl restart powernode-worker@default
Worker drains jobs before stopping (~28s). Do not proceed to health check for 30 seconds.
worker-web (always restart with worker)
sudo systemctl restart powernode-worker-web@default
frontend
sudo systemctl restart 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 30 seconds before health checks:
sleep 30
Step 4: Health Check
bash scripts/health-check.sh
If any checks fail, report which services are down and suggest remediation.
Step 5: Smoke Test (optional)
If all health checks pass, run a quick API smoke test:
curl -s http://localhost:3000/api/v1/health | python3 -m json.tool
curl -s http://localhost:4567/health | python3 -m json.tool
Step 6: MCP Connectivity (optional)
If MCP-related changes were made:
bash scripts/mcp-smoke-test.sh
Step 7: Report
| Service | Status | Details |
|----------------|--------|------------------|
| Backend | ✅/❌ | reload/restart |
| Worker | ✅/❌ | drain time |
| Worker Web | ✅/❌ | port 4567 |
| Frontend | ✅/❌ | port 5173 |
| API Health | ✅/❌ | HTTP status |
| Worker API | ✅/❌ | HTTP status |
| MCP | ✅/❌/⏭ | if tested |
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.
- yesterday First seen · 93 lines · 11 tokens per session scan D 863acf8c6ba5
deploy is a skill published in the GitHub repository nodealchemy/powernode-platform (2 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 576 once invoked, about $0.0001 per session on Opus 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
good-first-issue-batch
File a batch of contributor-ready GitHub issues from the seeds backlog, re-verifying every candidate against HEAD first so no dead issue reaches a contributor. Activate for prompts like "file some good first issues", "open a batch of GFIs", "publish backlog issues to GitHub", "find contributor-ready work", or after an…
seeds-issue-audit
Audit and triage open Seeds (sd) issues — find which can be closed, auto-close high-confidence completed ones, and report borderline cases. Activate for prompts like "audit open issues", "which seeds issues can be closed", "clean up the issue tracker", "triage the seeds backlog".
os-eco-dep-sync
Bump warren onto the latest published @os-eco/ versions across package.json + bun.lock and the Dockerfile CLI pins, then run the gates and open a PR. Use when checking if warren is on the newest burrow/plot/canopy/seeds/mulch/sapling.
release
Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.
warren-dogfood-pipeline
Full prioritize → dispatch → shepherd → track pipeline against the live warren instance. Audits the seeds backlog around a focus theme, dispatches the surviving issues to warren agents one at a time, babysits the resulting PRs to merge (update-branch, conflict-repair runs, auto-merge), and closes the loop in the…
canvas
Display HTML content on connected Mayros nodes (Mac app, iOS, Android).