jev-harness
Related Servers
Alternatives to jev-harness
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA universal interceptor that sits between any AI model's tool calls and shell execution, routing them through a supervisor daemon that inspects AST deltas, subprocess output, and hash-chained ledgers before work is allowed. It enables users to kill deleted assertions, trivial stubs, phantom test runs, and cyclic self-debate loops deterministically at the compiler, process, and filesystem boundaries rather than via prompt instructions.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to perform zero-token static audits, simulate refactorings in an ephemeral RAM clone, trace downstream ripple effects, and block unsafe writes with automatic rollback to prevent regressions.311 npmBusiness Source 1.1
- AlicenseAqualityAmaintenanceMartinLoop is the independent governance and financial control layer for AI coding agents. Set hard spend limits, prevent runaway loops, enforce verification, trigger rollback on failure, and generate auditable receipts showing what changed, what it cost, and whether the work passed.24385 npm394Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA runtime gate for coding agents. Blocks the tool calls that wreck a repo (force-push main, rm -rf, secret exfiltration, CI wipe) and lets normal build and commit work through. Machine-checked git-branch core (z3); the rest is high-precision heuristics. Tested on 3,790 real CI commands, 0 false blocks.1MIT

aperion-shieldofficial
FlicenseAqualityAmaintenanceLocal guardrail proxy for AI coding agents. Wraps any MCP server (stdio or HTTP/SSE) and blocks destructive tool calls before they execute, with TOFU catalog pinning against rug pulls and tool-poisoning/result-injection scanning. Single Rust binary, Apache-2.0.1411-- AlicenseBqualityBmaintenanceEnables coding agents to run budgeted tests and checks under a countdown with a stop rule, shape long logs into concise failure summaries, and guard pre-existing test files against silent assertion rewrites. It also delivers relevance-filtered project memory and renders a token-and-time roadmap of the orchestrator and every subagent spawned for a task.7MIT
TDQS
Scored across 6 tools
Each tool targets a distinct decision point in the agent workflow: triage failure, check abort, route task, verify completion, modulate reasoning, and evaluate nudge. The only potential overlap between route_task and modulate_reasoning_effort is well-clarified by descriptions that distinguish tier selection from per-call reasoning parameter mapping.
All tool names follow a consistent jev_ prefix with snake_case verb_noun or verb_noun_noun structure (e.g., jev_triage_test_failure, jev_route_task). No deviations in style or convention.
Six tools is well-scoped for an agent harness, with each tool addressing a unique decision point without redundancy. The set is neither too thin nor too heavy for the purpose.
The tools cover the core agent lifecycle decisions: model routing, reasoning effort, failure triage, abort detection, completion verification, and nudge evaluation. A minor gap exists in explicit state or attempt history management, but agents can work around this externally.