Model Alias Append

Automatically appends the model alias to the end of every response with integrated hook functionality and configuration change detection. Use when transparency about which model generated each response is needed. Use when: providing model transparency, tracking which model generated responses, monitoring configuration changes, or ensuring response attribution.

This skill appears to do what it says: it reads your OpenClaw configuration to map model IDs to aliases, appends aliases to responses, and watches the config for changes. Before installing or enabling the hook, consider: 1) Back up your ~/.openclaw/openclaw.json — the manage-hook script will write to it to toggle the response-alias-injector entry. 2) Review your openclaw.json for any sensitive fields (the skill reads that file) and ensure you're comfortable with a skill reading it. 3) The skill does not make network requests or request secrets; however, only install from a source you trust (the package metadata points to a GitHub repo). 4) If you prefer not to have any package modify your global config, avoid calling the enable/disable hook methods — you can enable the hook manually in your config instead. Overall this package is internally consistent with its description.

Type: OpenClaw Skill Name: model-alias-append Version: 1.0.2 The skill 'model-alias-append' is designed to append model aliases to agent responses and monitor OpenClaw configuration changes. Its code (`hooks/response-alias-injector/handler.js`, `main.js`, `scripts/manage-hook.js`) primarily interacts with the `openclaw.json` configuration file, reading it to extract model aliases and detect modifications, and writing to it to enable/disable its own hook. The use of `fs` and `child_process` modules is confined to these legitimate configuration management tasks, with no evidence of data exfiltration, arbitrary command execution, persistence mechanisms, or prompt injection attempts in any of the analyzed files.