refine-gate

A prompt-checking gate that notices unclear references or work requests without concrete code locations. It then asks for the missing context and defines what should count as a successful result.

In plain words
What is it for?
Use it to clarify bug reports, fixes, and build requests by identifying the relevant artifacts, separating symptoms from goals, choosing an approach, and setting verifiable completion criteria.
Why use it?
It reduces mistakes caused by phrases such as “like before” or “the broken solution” when the agent cannot know exactly what they mean. It helps connect the request to specific files, decisions, and acceptance checks before coding starts.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add cdeust/session-optimizer
agentmods
npx agentmods add plugins/cdeust/session-optimizer/refine-gate
Clone the repo
git clone --depth 1 https://github.com/cdeust/session-optimizer

Made for: Claude Code.

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

refine-gate 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 yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

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.

plugins/refine-gate/.claude-plugin/plugin.json · 21 lines

What it actually says

{
  "name": "refine-gate",
  "description": "Prompt-binding gate for Claude Code: a UserPromptSubmit hook detects prompts carrying unbound references (\"the SSE solution\", \"like before\", \"still broken\") or ungrounded work requests, and injects the /refine procedure — build a binding table with evidence, separate symptom from goal, select an execution strategy from a research-backed table (15 strategies verified against 2024-2026 literature, counter-evidence included), and define acceptance criteria as external signals.",
  "version": "2.1.0",
  "author": {
    "name": "Clement Deust",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/cdeust/session-optimizer",
  "repository": "https://github.com/cdeust/session-optimizer",
  "license": "MIT",
  "keywords": [
    "claude-code",
    "prompt-engineering",
    "refine",
    "intent-binding",
    "userpromptsubmit",
    "execution-strategy"
  ]
}
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. yesterday First seen · 21 lines scan A b93fefab54fb

Subscribe to this mod's changes

refine-gate is a plugin published in the GitHub repository cdeust/session-optimizer (1 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.