Verify config

Skill zapgun-ai/clawback/.skills/verify-config

Tokenmaxxing Gateway for Claude Code

Install

npx -y skills add zapgun-ai/clawback --skill verify-config

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Config doctor for clawback — loads the merged config (DEFAULTS < global < ./CLAWBACK.md < CLI overrides) exactly as the proxy's loadConfig does, prints a secret-free summary of the resolved values plus the merge-order sources, and exits non-zero if the canonical CLAWBACK.md did NOT take effect (host not 0.0.0.0, tls off, or adminToken missing) so a bad parse fails loudly instead of silently falling back to loopback defaults. Read-only; never prints the adminToken value, only its length. Use to confirm a CLAWBACK.md edit actually parsed and merged before starting the proxy, or to debug which config layer won.

SKILL.md

2.2 KB, 387 tokens by cl100k_base, as published. Nobody here has run it

clawback config doctor

Run .skills/verify-config/scripts/verify_config_parse.mjs from the project root. It loads the merged config the same way the proxy would and prints what actually resolved — no secrets — then fails loudly if the canonical CLAWBACK.md did not take effect.

node .skills/verify-config/scripts/verify_config_parse.mjs              # resolve from ./ (cwd)
node .skills/verify-config/scripts/verify_config_parse.mjs /path/to/project

The optional positional argument is the directory to resolve config from (defaults to the current working directory).

What it prints

sources (merge order) — each contributing tier and file path, lowest precedence first, exactly the layering in CLAUDE.md's Config Merging Strategy (DEFAULTS < global < local < CLI).
resolved — host, port, tls, cert/key paths, selfSign, passthrough, keepAliveEnabled, injectExtendedCacheTtl, adminPathPrefix, and whether an adminToken is present (length only — the value is never shown).
warnings — any non-fatal notes loadConfig surfaced.

Exit status

Exits non-zero with a FAIL: list when any of these are off — the signature of a CLAWBACK.md that did not parse or merge:

host is not 0.0.0.0 (the canonical LAN bind did not stick),
tls is not true,
adminToken is missing (a non-loopback bind would have thrown anyway).

Otherwise it prints OK: canonical CLAWBACK.md parsed and merged. Pairs with the write-config skill, which generates that file.

What ships with it: 1 file

2.1 KB alongside SKILL.md, 1 of them executable

scripts/

verify_config_parse.mjsruns2.1 KB