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/commit/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/commit)<a href="https://agentmods.dev/skills/nodealchemy/powernode-platform/commit"><img src="https://agentmods.dev/badge/skills/nodealchemy/powernode-platform/commit/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/commit"><img src="https://agentmods.dev/badge/skills/nodealchemy/powernode-platform/commit.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.00009 | $0.01006 |
| Opus 5.5 | $0.00004 | $0.00402 |
| Sonnet 5.5 | $0.00002 | $0.00201 |
| Haiku 4.5 | $0.00001 | $0.00101 |
Grade A, and why
commit 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staged Commit Workflow
Create logical, grouped commits from all current changes. Follow this process exactly:
Step 0: Verify CWD & Submodule State
Before analyzing changes, verify the working state:
pwd— confirm you are in the project rootgit rev-parse --show-toplevel— confirm parent repo identitygit submodule status— check all submodule pointers
If any submodule shows a + prefix (modified pointer), note it — this must be committed after the submodule's internal commits.
Step 1: Analyze Changes
Run these commands in parallel:
git status— see all changed/untracked files in the parent repogit diff --stat— see change summary for tracked filesgit diff --cached --stat— see already-staged changesfor d in extensions/*/; do git -C "$d" status --short; done— changes in each extension submodule (the public ones and any private extension a maintainer has added)git log --oneline -5— see recent commit style
Step 1.5: Pre-commit Safety Scan
Before creating any commits:
- Extension file leak: Check
git statusoutput for any files underextensions/*/staged in the parent repo. These MUST be committed inside their submodule, not the parent.- If found: Unstage them (
git reset HEAD extensions/...) and commit inside the submodule instead
- If found: Unstage them (
- Ruby syntax gate: If there are staged
.rbfiles, verify:git diff --cached --name-only -- '*.rb' | head -5 | xargs -I{} ruby -c {} - TypeScript gate: If there are staged
.ts/.tsxfiles, verify:cd frontend && npx tsc --noEmit 2>&1 | tail -5
Step 2: Group Files by Concern
Group changed files by concern: one commit per logical change, keeping a fix or feature together
with its migration, specs, and docs. Use these areas to spot unrelated changes that belong in
separate commits, not as the commit boundaries themselves: migrations (db/migrate/), models,
services, controllers and routes, frontend (frontend/src/), tests, seeds and config
(db/seeds/, config/, .claude/, scripts/), documentation (docs/, *.md, only if
explicitly 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.
- 1mo ago Changed · -3 lines 31dbcdeaf8dc
- 2mo ago First seen · 88 lines · 9 tokens per session scan A ddd496fafcf0
commit is a skill published in the GitHub repository nodealchemy/powernode-platform (4 stars, last pushed 5d ago), licensed MIT. It adds 9 tokens to every session and 1,006 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.
Other skills, from other repositories
gaia-badge-provision
Procedure for controlled, human-gated outbound README badge provisioning PRs (Issue #1817). Preflights upstream repositories, ensures single-badge placement with deep links, and records campaign outcomes without automated retries or multi-badge noise.
pr
Push committed changes and create a draft PR on GitHub. Use when you have staged changes ready to push and want to open a draft PR for early feedback or documentation.
fp-implement
Implement a scoped feature-pipeline plan in coherent commits and push each meaningful unit. Use for "implement the plan", "apply the plan", or the implementation stage; routine lean/economy work does not require planApproved, while explicit human gates remain binding.
regen
Manually trigger artifact regeneration, versioning, and chore commit. Use when you need fine-grained control over when registry artifacts sync (outside the automated sync-artifacts.yml workflow).
gaia-steward-land
Land a Gaia Steward Class A repair (agent-skill mirror or bundled-schema mirror) as a deterministic commit on a steward/a/ branch, open a draft PR to the integration branch, and record the outcome. Use when a full Steward run emits a forge.openpr action, for "land the class A repair", or "open the steward PR". Never…
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.