powernode-platform: Skill for Claude Code

.claude/skills/verify/SKILL.md

verify is a skill for Claude Code from nodealchemy/powernode-platform. It costs 12 tokens per session (845 once invoked), scanned A, original, MIT.

A verification command that chooses focused checks based on the files changed since the last commit. A commit is a saved checkpoint in version control.

In plain words
What is it for?
Use it after edits to run relevant syntax checks, type checks, tests, and related checks for the changed code.
Why use it?
It makes checking changes quicker than a full validation run while still testing the affected parts, such as Ruby, TypeScript, migrations, or seed data.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

This is nodealchemy/powernode-platform's own configuration. It tells Claude Code how to work on powernode-platform itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything powernode-platform configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/nodealchemy/powernode-platform/develop/.claude/skills/verify/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/nodealchemy/powernode-platform

Made for: Claude Code.

Wrote 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.

agentmods badge for verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/nodealchemy/powernode-platform/verify/github.svg)](https://agentmods.dev/skills/nodealchemy/powernode-platform/verify)
Your own site
<a href="https://agentmods.dev/skills/nodealchemy/powernode-platform/verify"><img src="https://agentmods.dev/badge/skills/nodealchemy/powernode-platform/verify/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.

agentmods 80×15 button for verify

Your own site · 80×15
<a href="https://agentmods.dev/skills/nodealchemy/powernode-platform/verify"><img src="https://agentmods.dev/badge/skills/nodealchemy/powernode-platform/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 845 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original 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.1 $0.00012 $0.00845
Opus 5.5 $0.00005 $0.00338
Sonnet 5.5 $0.00002 $0.00169
Haiku 4.5 $0.00001 $0.00085

Measured 1mo ago against content hash 50f311adbe3b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

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/verify/SKILL.md · 97 lines

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)

  1. Syntax check all changed .rb files:
    ruby -c <file>  # for each changed file
    
  2. Find related specs: Map each changed source file to its spec:
    • app/models/foo.rb → spec/models/foo_spec.rb
    • app/services/foo.rb → spec/services/foo_spec.rb
    • app/controllers/api/v1/foo_controller.rb → spec/requests/api/v1/foo_spec.rb or foo_controller_spec.rb
  3. 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)

  1. Type check the full frontend project:
    cd frontend && npx tsc --noEmit
    
  2. Find related tests: Look for *.test.ts or *.test.tsx alongside changed files
  3. Run related tests (if they exist):
    cd frontend && CI=true npm test -- --testPathPatterns "<pattern>" --watchAll=false
    

Step 4: Migration Verification (if migration files changed)

  1. Check migration status:
    cd server && bundle exec rails db:migrate:status
    
  2. If any migrations are down, run them:
    cd server && bundle exec rails db:migrate
    

Read the full file on GitHub · 97 lines

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. 1mo ago Changed 50f311adbe3b
  2. 2mo ago First seen · 97 lines · 12 tokens per session scan A 686702202766

Subscribe to this mod's changes

verify is a skill published in the GitHub repository nodealchemy/powernode-platform (4 stars, last pushed 5d ago), licensed MIT. It adds 12 tokens to every session and 845 once invoked, about $0.0000 per session on Opus 5.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.

Related

Other skills, from other repositories

agent-evals

A method for testing AI agents by examining what they actually did during a run, including their tool use and execution steps. It also covers building test cases from real production runs and comparing automated judgments with human labels.

ssheleg/agent-stack · 76 tokens

agent-puzzles

Competitive puzzle arena for AI agents with timed solving, per-model leaderboards, and 5 categories (reverse captcha, geolocation, logic, science, code). Use when solving puzzles, tracking rankings, creating new challenges, or benchmarking agent capabilities.

ThinkOffApp/ide-agent-kit · 53 tokens

benchmark-critic

Evaluate benchmark design for fair baselines, measurable outcomes, leakage, cherry-picking, and reproducibility.

cherninlab/ennodia · 25 tokens

release-readiness

Check whether a change is ready for a public release candidate across packaging, docs, tests, and rollback risk.

cherninlab/ennodia · 26 tokens

ev-benchmark-verification

Phase 2B of the Gaia evidence verification pipeline. Verifies benchmark-result rows and benchmark-source candidates against registry/benchmark-sources.json before adversarial audit, link validation, catalog promotion, or ingestion. Use when running /ev-pipeline, checking benchmark-result evidence, reviewing…

gaia-research/gaia-skill-tree · 78 tokens

fp-review

Adversarially review the full relevant PR diff with isolated probes and meaningful before/after checks. Use for "review the PR", "sandbox review", or the review stage; retain required reviewer independence and report self- review limits honestly.

gaia-research/gaia-skill-tree · 51 tokens