RavenRepo

Jevengineeringgate — AI skill for Claude Code

AI community

Calibrated decision layer and risk gate for AI coding agents.

How to install Jevengineeringgate

This entry records only its repository, not the path inside it, so there is no exact command to give. Open RavenRepo/jevengineeringgate and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Jevengineeringgate does

Calibrated decision layer and risk gate for AI coding agents. Routes yes/no, routing and scoring judgments to the Jev System One model at ~$0.0000123 per decision, then enforces the result deterministically through Claude Code PreToolUse hooks. Fitted thresholds, not guessed.

Alternatives in AI

  • Om Humanize — Voice-calibrated editing — makes Claude-drafted text sound like you wrote it, not like AI wrote it 4.6k ★
  • Creative Director Skill — AI creative director with recursive self-assessment: 20+ methodologies (SIT, TRIZ, Bisociation, SCAMPER, Synec 32 ★
  • Agent Yes — Run AI coding agents (Claude, Codex, Gemini …) unattended — auto-answer prompts, auto-retry on rate limits, an 29 ★

README

jevengineeringgate — a calibrated decision layer and risk gate for AI coding agents

[![CI](https://github.com/RavenRepo/jevengineeringgate/actions/workflows/ci.yml/badge.svg)](https://github.com/RavenRepo/jevengineeringgate/actions/workflows/ci.yml) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) [![Node.js](https://img.shields.io/badge/node-%3E%3D18-brightgreen.svg)](https://nodejs.org) [![Decisions cost](https://img.shields.io/badge/per%20decision-~%240.0000123-blue.svg)](#measured-cost)

**An LLM creates the work. Something else should decide what happens next.**

Every AI agent has the same leak: a frontier model sits in a loop answering yes-or-no, picking the next worker, and scoring relevance. Those calls never needed generation. This repository moves them to [Jev](https://typesafe.ai), the System One decision model from TypeSafe AI — and then **enforces the result deterministically**, as host hooks rather than as a rule an agent has to remember.

LLM generates  →  Jev decides  →  code executes  →  humans handle uncertainty
  • ~292 input tokens, ~0.98s, ~$0.0000123 per decision (measured, not quoted)
  • Thresholds are fitted, not guessed — a sweep over 26 labeled cases
  • 0 wrong, 0 unsafe, 25/26 primary-label hits at the current operating point
  • 48 offline tests, no API key required to run them

Why a prose rule is not a gate

Most agent setups put the guardrail in an instruction file:

*"Before any risky, destructive, or irreversible action, run the risk gate."*

That cannot work. It asks the agent to **already know the action is risky** — which is the exact judgment the gate exists to make. The gate only fires when it was not needed.

A [`PreToolUse` hook](docs/jev.md) does not need to be remembered. It runs on every tool call, before execution, and returns `deny`, `ask`, or nothing.

Install

git clone https://github.com/RavenRepo/jevengineeringgate.git
cd jevengineeringgate
npm