ConfigChange

ConfigChange is a hook for coding agents from silouone/clens. Its token cost is not measured, scanned A, original, MIT.

A configuration hook that runs the `clens-hook ConfigChange` command whenever a configuration change event occurs. A hook is an automatic action triggered by a specific event.

In plain words
What is it for?
It is for connecting configuration-change events to the clens hook command in an agent or application configuration.
Why use it?
It keeps configuration-change handling automatic, so the related command does not have to be started manually each time settings change.

Hook

Part of the clens plugin — 5 skills, 3 commands, 1 agent, 18 hooks shipped together

One of 18 entries in hooks.json — they are configured in one file and arrive together.

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add hooks/silouone/clens/config-change
Clone the repo
git clone --depth 1 https://github.com/silouone/clens

Or install clens, the plugin that ships this one along with the rest of its 5 skills, 3 commands, 1 agent, 18 hooks.

Wrote this? Show the measurements

A badge for your README with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them.

agentmods badge for ConfigChange

README.md
[![agentmods](https://agentmods.dev/badge/hooks/silouone/clens/config-change.svg)](https://agentmods.dev/hooks/silouone/clens/config-change)
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

ConfigChange 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 3d ago.

A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

packages/cli/agentic/hooks/hooks.json · 12 lines

What it actually says

{
  "ConfigChange": [
    {
      "hooks": [
        {
          "type": "command",
          "command": "clens-hook ConfigChange"
        }
      ]
    }
  ]
}
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.

  1. 3d ago First seen · 12 lines scan A 2b2c3823b6df

Subscribe to this mod's changes

ConfigChange is a hook published in the GitHub repository silouone/clens (6 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: a hook is shell that never enters the context. 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.