catalyst-refusal-watch by TransmuteLabs: Claude Code mod code

What it does

Draws the status line
Watches TaskStop calls and can refuse them
Hooks prompt.context, session.end, session.start, settings.read and 3 more
Keeps its own state between turns

Good points

No network calls
Starts no processes
Written in TypeScript
Handles errors

Code to start from

A starter ModsCode writes from the drawing it read, and the mod's own lines that draw, where there are any.

Starter (register.tsx)

import type { Register } from 'claude-code'

// Drawn like catalyst-refusal-watch by Marat Karimov (status, toast), as ModsCode read it from the mod's code:
// https://modscode.com/claude-mods/mods/transmutelabs-catalyst-refusal-watch/
// Written by ModsCode from that reading, not copied from the mod: use it as you like.
// Each value below stands for one the mod works out at run time; put in your own.
export const register: Register = on => {
  on('session.start', async ($, e, next) => {
    const hhmm = '…'
    await $.ui.status(`⚠ обрывов фильтром за сессию: 0 · последний ${hhmm}`)
    return next(e)
  })
}

The mod's own code

No drawing lines were cut from this mod's code; its source is linked.

TransmuteLabs/Catalyst

How to build this: Status line, Deny a tool call

What its code calls

env varstool callsremembers

What its code shows

Read from the source at commit 59ec0fa53ada on 2026-10-11. The first group decides whether a mod is listed; the rest is for you to weigh. A later commit is not read until the next crawl.

Decides the listing: code you can check
Entry read	Every module hooks/hooks.json names was read.plugins/catalyst-refusal-watch/hooks/register.ts
Parses	Every file parses as TypeScript or JavaScript.1 files parsed
All its code is in the mod	Every import is a file of the mod or the engine's own module; no packages, no require.all its code is in the mod
Readable	No minified lines, no eval or new Function, no import of a computed path, no encoded blobs.no minified code, no eval, no encoded blobs
Calls in the open	Network and programs are reached as $.http.fetch and $.process.run in place, never passed around.every call outside goes through $ in the open
For you to weigh before installing
Where it draws	The terminal, the desktop app, both, or nothing (hooks only: a guard or a prompt rewriter), as its code says. Shown, never a reason to leave a mod out.draws in the terminal and the desktop app, the same in both
Install line	Whether its repository's own .claude-plugin/marketplace.json lists it, so it installs from that marketplace with the lines on its page.listed in its repository's .claude-plugin/marketplace.json: installs from there
Programs on Windows	Whether every program it starts through $.process exists on Windows (tail, date, open, osascript, /usr/… do not).runs no program a Windows PC lacks
Network	Whether every fetch names its https host in the code.no network
Programs	Whether every program it starts is named in the code and is not a shell, an interpreter or a network tool.starts no programs
Reads and sends	Whether it both reads something of yours (files, environment variables, the transcript, settings) and reaches outside (the network, an MCP server, another session, telemetry).reaches no network
Keys in the source	Whether the source holds what looks like an API key or a private key.no keys in the source
Licence	An open licence (MIT, Apache-2.0, BSD, ISC, Unlicense, 0BSD, CC0) with its text lets ModsCode show its code; otherwise the code is linked.no licence

This is a reading of the code text, not a security review: it does not run the mod, and it cannot see what a program the mod starts does. The check before installing is yours. How mods are chosen

Install it

Check it yourself before you install it. Mods run unsandboxed, with your permissions, and ModsCode does not vouch for what this code does. Read its code (or run claude plugin validate . in its folder), weigh what it reaches, and install the commit you read.

From its marketplace

Its repository is its marketplace. Add that marketplace (in the terminal with these commands, or in the desktop app's plugin settings) and install the mod from it:

/plugin marketplace add TransmuteLabs/Catalyst

/plugin install catalyst-refusal-watch@catalyst

/reload-plugins

This installs the marketplace's latest commit, which may not be the one read here (59ec0fa53ada). Compare them before you install. /reload-plugins loads it into a session that is already open.

Try the commit ModsCode read

No marketplace needed. In a terminal, clone the repository, check out the commit read, validate the mod, and load it for one session:

git clone https://github.com/TransmuteLabs/Catalyst

git -C Catalyst checkout 59ec0fa53adaaedda2438f84a179e8259c55f597

claude plugin validate Catalyst/plugins/catalyst-refusal-watch

claude --plugin-dir Catalyst/plugins/catalyst-refusal-watch

The validate line lists the events the mod hooks and what it asks Claude Code to do, without running it. The last line loads the mod for this session only and writes nothing to your settings. If the author has rewritten history, the commit may no longer exist.

Ask Claude about it

With the ModsCode connector added, Claude can read this mod's code and what it reaches, and build on them. Ask it like this:

Read the ModsCode mod "transmutelabs-catalyst-refusal-watch" with its code and make me one like it

Search them from Claude: the MCP connector

Similar mods

Badge for your README

If this is your mod, paste this into your README. It links to this page.

README.md

[![ModsCode](https://modscode.com/badge/transmutelabs-catalyst-refusal-watch.svg)](https://modscode.com/claude-mods/mods/transmutelabs-catalyst-refusal-watch/)