DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to get clearer Claude Code answers via the Stop hook with Nopus

Install the Nopus plugin so Claude Code requests one clearer rewrite when an answer turns abstract.

Who it is forA developer using Claude Code who gets long answers full of abstract wording and needs them shorter to act on.

The problemCoding-agent answers drift into abstract LLM babble that is hard to act on.

The outcomeResponses that cross the chosen sensitivity threshold receive one clearer rewrite request from the Stop hook.

What you need first

  • Node.js 22 or newer with the `node` command available
  • One supported coding agent installed: Pi, Claude Code, or Codex
  • Permission to add a plugin or marketplace in the chosen agent

Steps

  1. Make sure Node.js 22 or newer is installed and the node command is available.
  2. Run /plugin marketplace add Vistyy/nopus in Claude Code.
  3. Run /plugin install nopus@nopus.
  4. Run /nopus:nopus-configure medium to set the default sensitivity.
  5. Ask Claude Code a question that produces a long explanation and check whether the message "Nopus requested a clearer rewrite." appears when a rewrite is requested.

Prompt for your agent

Using the nopus repo at Vistyy/nopus, add the marketplace with `/plugin marketplace add Vistyy/nopus`, install with `/plugin install nopus@nopus`, and set sensitivity with `/nopus:nopus-configure medium` in <project directory>. Expected output: a confirmed plugin install and a saved medium sensitivity setting. Verify that the message "nopus requested a clearer rewrite." appears after a long, abstract answer.

Caveat. The published rewrite rates of 5.3% to 18.6% come from 5,337 Pi responses, so Claude Code results may differ.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page