mcpbeat Sign in

Stop That Shit Skill for Codex

Keep Codex focused on requested and necessary work. Use for bounded changes, review-only tasks, scope creep, speculative hardening, unnecessary hashing or dependencies, repeated audit loops, or when the user invokes Stop That Shit.

746 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
111
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/lennney/stop-that-shit --skill stop-that-shit

What comes with it

263 bytes besides the instruction
agents/openai.yaml

What it tells the agent to use

found in the instruction text
Task spawns other agents

The instruction itself

4 sections, as written by the author

Stop That Shit

Do the requested work. Keep necessary consequences. Stop everything else.

This Skill is advisory and works without the Guard hooks. It cannot guarantee

model behavior. When the Guard is installed, the same directives also provide

machine-enforced boundaries on supported Codex Hook paths.

Follow the Stop Ladder

Before adding work that the user did not name, ask:

  • Did the user request it?
  • Is it necessary to complete the requested result?
  • What reachable code, data, deployment state, or acceptance proves that need?
  • Would omitting it fail the current task?

If the answer remains no, do not implement it. Report it only when useful.

Keep necessary callers, fixtures, tests, accessibility, security, compatibility,

and migration work when reachable evidence requires them. Fewer files or lines

is not the goal. The smallest correct result is.

Respect the task mode

  • review, answer, and monitor are read-only unless the user authorizes a

change.

  • change permits only requested work and necessary consequences.
  • Do not add hashing, a dependency, a compatibility layer, a migration, an

abstraction, or a subagent merely because it might help later.

  • Do not repeat searches, tests, or reviews after the requested result has enough

evidence.

With Skill only, treat the mode as an instruction. With Guard installed, use:

$stop-that-shit change -- Fix the failing config test.
$stop-that-shit review -- Review this diff. Report findings; do not edit.

An installed Guard begins in observation-only unconfirmed mode. Do not claim

that an action was blocked unless an explicit mode armed the Guard and the Guard

returned permission deny. Even then, describe the host effect as unobserved.

The following inspection commands do not change the current task contract:

$stop-that-shit status
$stop-that-shit runtime
$stop-that-shit explain evt_...
$stop-that-shit label evt_... correct|incorrect|inconclusive

Use a hard file lock only when the complete boundary is already known:

$stop-that-shit lock change files=src/config.cjs|test/config.test.cjs -- Fix this behavior.

Do not invent a file list to appear precise. Inspect proportionately and explain

material expansion before acting.

Finish

Report the requested result, necessary consequences, and the evidence that makes

the task complete. Do not add a final audit loop only to satisfy this Skill.

How to use it

Copy the folder

Take lennney/stop-that-shit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.