← Search

Change Verifier
Finance 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit cbee934
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: Node.js to build.

Change Verifier

Seven checks before anyone changes who a company pays

At a glance
What
Seven checks before anyone changes who a company pays
Cost
Free
Needs
Node.js to build. Hosting (Vercel or your own server) for the web UI.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @naileditnorthshore-lab
Creator of Change Verifier, a free open-source (MIT) Muse connector that gates bank-detail changes behind seven checks. Curated listing — credit to the creator.

Quick answer

Change Verifier is a free Muse skill that runs seven checks on bank-detail changes, saying clear, review, or block, and holding the change until a named owner accepts it. It is a connector with a Streamable-HTTP MCP server plus controller UI, but it is not a payment system, since it never touches a bank or ERP.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit cbee934

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Node.js to build. Hosting (Vercel or your own server) for the web UI. No GitHub account needed unless listed here. Install "Change Verifier" for me. A web app plus an MCP route for reviewing batches of code changes with verdicts and evidence. Repository: https://github.com/naileditnorthshore-lab/change-verifier Pinned version: install the code at commit cbee934afe5060168e29e93b01723d3e157b4b27 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone the repo into a temporary folder (public HTTPS clone — no account needed) and look inside. 2. Safety check: briefly review any scripts for anything suspicious (network calls to unexpected hosts, shell commands, credential harvesting). If you see a red flag, stop and tell me before going further. 3. Build it per its README. Then lay out my options honestly: run it locally, or deploy it (e.g. Vercel / my own server) — with the exact steps for the option I pick. Don't start a long-running server without asking me first. 4. Verify without network calls: the build succeeds. 5. Report: what you installed, where, and anything still left for me to do myself (or confirm there's nothing left). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it (e.g. authenticated clone); otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit cbee934 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

Free and open-source (MIT): https://github.com/naileditnorthshore-lab/change-verifier — Streamable-HTTP MCP server plus controller UI; deploy on a public HTTPS origin, then submit at muse.ai/platform.
✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
cbee934 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.