effort-prefix by mako-code: Claude Code mod code

What it does

Draws toasts
Hooks prompt.submit, session.end, turn.complete, turn.start and 1 more

Good points

No network calls
Starts no processes
Small: 192 lines
Written in TypeScript

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 effort-prefix by mako-code (toast), as ModsCode read it from the mod's code:
// https://modscode.com/claude-mods/mods/mako-code-effort-prefix/
// 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 level = '…'
    const model = '…'
    await $.ui.toast(`effort: ${level} for this turn`)
    await $.ui.toast(`${model} has no effort setting; the prefix does nothing here.`)
    return next(e)
  })
}

The mod's own code

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

mako-code/gobworks

How to build this: Toast, Rewrite the prompt

What its code calls

nothing found

What its code shows

Read from the source at commit ec6ea2383749 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.mods/prompting/effort-prefix/hooks/register.tsx
Parses	Every file parses as TypeScript or JavaScript.2 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.MIT

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 mako-code/gobworks

/plugin install effort-prefix@gobworks

/reload-plugins

This installs the marketplace's latest commit, which may not be the one read here (ec6ea2383749). 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/mako-code/gobworks

git -C gobworks checkout ec6ea23837494b5b13124caa186450be8b42bf2d

claude plugin validate gobworks/mods/prompting/effort-prefix

claude --plugin-dir gobworks/mods/prompting/effort-prefix

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 "mako-code-effort-prefix" with its code and make me one like it

Search them from Claude: the MCP connector

Similar mods

More from this repository

See all 117 mods in this repository

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/mako-code-effort-prefix.svg)](https://modscode.com/claude-mods/mods/mako-code-effort-prefix/)