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/improve/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/improve)<a href="https://agentmods.dev/skills/nodealchemy/powernode-platform/improve"><img src="https://agentmods.dev/badge/skills/nodealchemy/powernode-platform/improve/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/improve"><img src="https://agentmods.dev/badge/skills/nodealchemy/powernode-platform/improve.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.00000 | $0.01197 |
| Opus 5.5 | $0.00000 | $0.00479 |
| Sonnet 5.5 | $0.00000 | $0.00239 |
| Haiku 4.5 | $0.00000 | $0.00120 |
Grade A, and why
improve 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/improve — Discover & Offer Code-Quality Improvements
Surface code-quality improvements, offer them for human approval, and turn approved ones into dev-improve Ralph Loop tasks that /dev-loop (or a platform agent) acts on. Operator-driven (Tier-1). The platform improvement MCP tool is the dual surface — platform agents call the same actions, so this works for Powernode and any other indexed repo.
Usage
/improve discover [repo] # find + vet + offer improvements
/improve review # list pending offers
/improve approve <id> # approve an offer -> creates a dev-improve task
/improve delegate <id> # approve + hand the task to a platform agent
/improve revert <id> # mark a promoted task reverted (ungameable metric signal)
/improve status # improvement scoreboard (velocity + revert_rate)
/improve enable-autonomy <agent> # gated: run dev-improve unattended (off by default)
/improve disable-autonomy # return dev-improve to operator-driven
discover
- Analyze (MCP-first):
platform.code_static_analysis, thenscripts/pattern-validation.sh; addplatform.code_dead_code/platform.code_find_duplicateswhen asked. - Verify-before-offer (scrutiny gate — mandatory): for EACH candidate, confirm it still reproduces on HEAD. For
dead_code/code_duplication, prove zero live callers withplatform.code_blast_radiusBEFORE proposing a deletion/extraction. Discard anything you cannot reproduce. Record the proof asverifier_evidence. - Classify each vetted finding:
code_lint | dead_code | code_duplication | convention_adherence | test_gap. - Core-purity (gate #9): findings under
extensions/private/*are auto-tagged to that extension by the tool — never offer them as core/global, and never propose a fix that makes a core file depend on an extension. - Offer each finding:
platform.create_improvementwithrecommendation_type,title,fingerprint(kind|file|rule),files,fix,verifier_evidence,confidence_score. Idempotent onfingerprint— re-runningdiscoverupdates, never duplicates. - Report a summary table (kind, title, file, confidence). Do NOT bulk-approve — offers await individual human review (CLAUDE.md bulk-op rule covers auto-discovered code 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.
- 1mo ago Changed 6be6a2abe5a0
- 2mo ago First seen · 61 lines · 0 tokens per session scan A a6d4071211d7
improve is a skill published in the GitHub repository nodealchemy/powernode-platform (4 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,197 tokens. 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
github_read
Read access: repos, issues, PRs, files, branches, workflows, runs.
accurate-code
Use when implementing or modifying code with Kontext Brain so each behavior-bearing logic unit is grounded in current provenance-backed decisions, domain terms, invariants, and Evidence.
rigorous-review
Review code, docs, or plans for correctness risks, missing evidence, unclear tradeoffs, and untested assumptions.
dev-review
Code-focused plan-bounce-execute workflow between Claude Code (Opus) and Codex CLI. Use when the user wants repo files changed, a bug fixed, a feature implemented, or a code plan verified before execution. One AI composes a plan, it bounces between agents with [CONTESTED]/[CLARIFY] markers until refined, then the…
gaia-curation-review
Review a Gaia curation PR or branch as a read-only merge gate. Use for canonical registry promotion, schema, evidence, prerequisite, nomenclature, installability, and generated-artifact checks. Route intake batches to /gaia-draft-curate and unrelated PRs to /review.
review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…