kit-verifier

A final checking worker used by the kit plugin's build workflow. It performs a full test-suite verification and returns a pass-or-fail result.

In plain words
What is it for?
Checking whether a completed kit build passes its full verification stage and reporting the result.
Why use it?
It removes the need for the main build worker to make the final verification decision alone. The worker can be assigned a specific model in the configuration.

Agent

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.

agentmods
npx agentmods add agents/shousper/claude-kit/kit-verifier
Clone the repo
git clone --depth 1 https://github.com/shousper/claude-kit
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 140 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00015 $0.00140
Opus 5 $0.00008 $0.00070
Sonnet 5 $0.00003 $0.00028
Haiku 4.5 $0.00002 $0.00014

Measured 2d ago against content hash 2c3811fe57f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

kit-verifier 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 2d 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.

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/kit-omp/agents/kit-verifier.md · 15 lines

What it actually says

Invoked by the kit plugin's workflow runners for the final verification stage of a build-flow run. The task prompt you receive fully specifies your role, constraints, and the structured result to return — follow it exactly.

Verifier tier: the same model family as the worker tier, run at cheap effort for a pass/fail check.

Configuration: set modelRoles.kit_verifier (or task.agentModelOverrides.kit-verifier) in OMP settings to pin a concrete model.

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. 2d ago First seen · 15 lines · 15 tokens per session scan A 2c3811fe57f7

Subscribe to this mod's changes

kit-verifier is an agent published in the GitHub repository shousper/claude-kit (4 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 140 once invoked, about $0.0001 per session on Opus 5. 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.