fast-claude-code

What to check before installing/using: - Review callback targets: examine what callback backend you'll use (openclaw, webhook, ntfy). webhook mode will POST JSON to any URL you supply or CC_WEBHOOK_URL—do not point this to untrusted endpoints. Prefer the platform's internal gateway (openclaw) if you want to avoid sending data to external servers. - Understand file writes and reads: team mode installs .claude/hooks/on-stop.sh and edits .claude/settings.json in your project. The on-stop hook enumerates files (up to a limit) and sends that list to the callback. If your repository contains sensitive files, run this only in a safe/test copy or inspect the hook first. - Avoid auto mode on sensitive projects: the scripts encourage --permission-mode auto / --dangerously-skip-permissions and even auto-accept permission prompts via tmux. This lets Claude run tools without interactive confirmation—do not use 'auto' in sensitive or production repositories. - Verify jq availability: team mode expects jq and will error out if missing even though metadata calls it 'optional'. Install jq or avoid team mode. - Obtain and protect session keys: you must supply a session-key to route callbacks. Treat that key as sensitive and do not hardcode it in public scripts. - Run in isolated environment first: test the skill in a disposable clone/container to observe exactly what it writes and sends before using it on real code. - Inspect the included hook (on-stop.sh) and callback scripts yourself: they are bundled with the skill and will be run on your filesystem—ensure you are comfortable with their logic and destinations. If you can't confirm the callback endpoints and are not prepared to run with the permission-bypass behavior, treat this skill as risky.