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/verifynpx skills add nodealchemy/powernode-platform --skill verifygit 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.00012 | $0.00848 |
| Opus 5 | $0.00006 | $0.00424 |
| Sonnet 5 | $0.00002 | $0.00170 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
verify 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/verify — Targeted Change Verification
Run focused quality checks based on what actually changed. Faster than validate.sh, more thorough than hooks.
Step 1: Detect Changes
If scope is auto or no argument provided, detect what changed:
# Changed Ruby files (unstaged + staged + untracked)
git diff --name-only HEAD -- '*.rb' 2>/dev/null
git diff --cached --name-only -- '*.rb' 2>/dev/null
git ls-files --others --exclude-standard -- '*.rb' 2>/dev/null
# Changed TypeScript files
git diff --name-only HEAD -- '*.ts' '*.tsx' 2>/dev/null
git diff --cached --name-only -- '*.ts' '*.tsx' 2>/dev/null
git ls-files --others --exclude-standard -- '*.ts' '*.tsx' 2>/dev/null
# Changed migrations and seeds
git diff --name-only HEAD -- 'server/db/migrate/' 2>/dev/null
git diff --name-only HEAD -- 'server/db/seeds/' 2>/dev/null
If a specific scope is given (ruby, typescript, migration, seed), only run that category.
Step 2: Ruby Verification (if .rb files changed)
- Syntax check all changed
.rbfiles:ruby -c <file> # for each changed file - Find related specs: Map each changed source file to its spec:
app/models/foo.rb→spec/models/foo_spec.rbapp/services/foo.rb→spec/services/foo_spec.rbapp/controllers/api/v1/foo_controller.rb→spec/requests/api/v1/foo_spec.rborfoo_controller_spec.rb
- Run related specs (only those that exist):
cd server && bundle exec rspec <spec-files> --format progress
Step 3: TypeScript Verification (if .ts/.tsx files changed)
- Type check the full frontend project:
cd frontend && npx tsc --noEmit - Find related tests: Look for
*.test.tsor*.test.tsxalongside changed files - Run related tests (if they exist):
cd frontend && CI=true npx react-scripts test --testPathPattern="<pattern>" --watchAll=false
Step 4: Migration Verification (if migration files changed)
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 · 97 lines · 12 tokens per session scan A 686702202766
verify is a skill published in the GitHub repository nodealchemy/powernode-platform (2 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 848 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
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).