holdout-evaluator

holdout-evaluator is a skill for Claude Code from synaptiai/synapti-marketplace. It costs 178 tokens per session (3,440 once invoked), scanned B, original, Apache-2.0.

A quality-checking skill that evaluates an agent's completed work against hidden test situations and produces evidence-based feedback. LLM-as-Judge means another language model assesses the result against set criteria.

In plain words
What is it for?
Use it to test work against unseen cases, compare claimed checks with actual files, and record evaluation feedback and telemetry.
Why use it?
It can reveal weak or unsupported claims that a normal self-review may overlook.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter; mentions subagents; names the AskUserQuestion tool.

Part of the ai-first-org-design-kit plugin — 15 skills shipped together

Good fit Use it to test work against unseen cases, compare claimed checks with actual files, and record evaluation feedback and telemetry.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/synaptiai/synapti-marketplace/holdout-evaluator
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.

Any agent
npx skills add synaptiai/synapti-marketplace --skill holdout-evaluator
Clone the repo
git clone --depth 1 https://github.com/synaptiai/synapti-marketplace

Made for: Claude Code.

Or install ai-first-org-design-kit, the plugin that ships this one along with the rest of its 15 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for holdout-evaluator

README.md
[![agentmods](https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/holdout-evaluator/github.svg)](https://agentmods.dev/skills/synaptiai/synapti-marketplace/holdout-evaluator)
Your own site
<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/holdout-evaluator"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/holdout-evaluator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for holdout-evaluator

Your own site · 80×15
<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/holdout-evaluator"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/holdout-evaluator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 178 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,440 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00178 $0.03440
Opus 5 $0.00089 $0.01720
Sonnet 5 $0.00036 $0.00688
Haiku 4.5 $0.00018 $0.00344

Measured 12d ago against content hash d4a0528b138c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade B, and why

holdout-evaluator scanned grade B with 1 finding 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 12d ago.

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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

chmod 700 "$HOME/.ai-first-kit" 2>/dev/null
plugins/ai-first-org-design-kit/skills/holdout-evaluator/SKILL.md · 257 lines

How it starts

The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Holdout Evaluator

You are a Quality Gate Judge — you evaluate agent work output against hidden holdout scenarios that the executing agent never sees. Your core insight: visible gate criteria tell agents WHAT to check, but holdout scenarios test WHETHER they genuinely understand the criteria or are just checking boxes.

You operate as an independent evaluator, never revealing holdout scenario content to the executing agent. Your output has two layers: a detailed layer for telemetry (which scenarios passed/failed) and a mapped layer for the agent (which visible criteria are weak, without naming scenarios).

Read ../../shared/concepts.md for the Artifact Handoff Convention and Governance Health Metrics.

Work through these steps in order, announcing each step as you begin it:

Persona

  • Skeptical. Claims without evidence are failures. "I verified X" without proof is the same as not verifying.
  • Behavioral. Evaluate what the output shows, not what the agent says it did. Look for signs of the failure mode, not just whether the right words are present.
  • Secure. Never reveal holdout scenario names, descriptions, or specifics in mapped output. The executing agent must not learn the test set.
  • Fair. Evaluate the work output, not the agent. A genuine effort that happens to exhibit a failure mode still fails — but the feedback should be constructive.

Pre-Flight

# Derive stable project slug from git repo root
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
if [ -n "$REPO_ROOT" ]; then
  SLUG=$(basename "$REPO_ROOT" | tr '[:upper:]' '[:lower:]' | tr ' ' '-' | head -c 40)
else
  SLUG=$(echo "${PWD##*/}" | tr '[:upper:]' '[:lower:]' | tr ' ' '-' | head -c 40)
fi
[ -z "$SLUG" ] && SLUG="default"
mkdir -p "$HOME/.ai-first-kit/projects/$SLUG/evolution"
chmod 700 "$HOME/.ai-first-kit" 2>/dev/null

# Check required artifacts
GATES_INDEX=$(ls "$HOME/.ai-first-kit/projects/$SLUG/gates/INDEX.md" 2>/dev/null)
HOLDOUT_COUNT=$(find "$HOME/.ai-first-kit/projects/$SLUG/gates/.holdouts/" -name "*.md" 2>/dev/null | wc -l | tr -d ' ')

[ -n "$GATES_INDEX" ] && echo "GATES: found" || echo "GATES: missing"
[ "$HOLDOUT_COUNT" -gt 0 ] 2>/dev/null && echo "HOLDOUTS: $HOLDOUT_COUNT files" || echo "HOLDOUTS: missing"

# Check for existing telemetry
TELEMETRY=$(ls "$HOME/.ai-first-kit/projects/$SLUG/evolution/gate-telemetry.jsonl" 2>/dev/null)
[ -n "$TELEMETRY" ] && echo "TELEMETRY: found ($(wc -l < "$TELEMETRY" | tr -d ' ') entries)" || echo "TELEMETRY: none (will create)"

Read the full file on GitHub · 257 lines

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. 12d ago First seen · 257 lines · 178 tokens per session scan B d4a0528b138c

Subscribe to this mod's changes

holdout-evaluator is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 178 tokens to every session and 3,440 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

debug

Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test. No features, no extra refactors.

jsmastery-pro/skills · 74 tokens

check

Confirm a change before merge. /check verify drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). /check review runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never…

jsmastery-pro/skills · 74 tokens

pipeline-efficiency-benchmark

A repeatable benchmark for comparing different versions of a development pipeline. It runs the same public tasks in isolated workspaces and records scores, tokens, time, tool calls, and cost.

KtKID/x-dev-pipeline · 131 tokens

x-qdev

A compact development workflow for a small, clearly defined code change. It keeps the requirement, initially failing tests, implementation, and real verification results in one task document, following TDD, or test-driven development.

KtKID/x-dev-pipeline · 116 tokens

x-adversarial-risk

A focused adversarial review of a software specification. It tries to find small counterexamples that would expose incorrect implementations, such as invalid state changes, crashes, duplicate actions, permission mistakes, or concurrent events.

KtKID/x-dev-pipeline · 85 tokens

x-qa-gate

A quality-review gate for completed development tasks. It checks the code against the request, design, tests, verification evidence, and current changes, using different review rounds for different risk levels.

KtKID/x-dev-pipeline · 140 tokens