agent-evaluation

agent-evaluation is a skill for Claude Code, Codex from ihatesea69/kiro-kit. It costs 61 tokens per session (1,170 once invoked), scanned A, original, MIT.

A toolkit for testing AI agents and chatbots with expected answers, expected tool choices, adversarial examples, and automated quality judgments. It also covers checks in continuous integration and monitoring for quality changes after release.

In plain words
What is it for?
Use it to build test sets, run offline evaluations, block unsafe changes before merge, evaluate retrieval-augmented systems on Amazon Bedrock, and watch production quality drift.
Why use it?
It provides a repeatable way to detect regressions, such as an agent choosing the wrong tool, mishandling prompt injection, or giving worse answers after a code change.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to build test sets, run offline evaluations, block unsafe changes before merge, evaluate retrieval-augmented systems on Amazon Bedrock, and watch production quality drift.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ihatesea69/kiro-kit/agent-evaluation
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 ihatesea69/kiro-kit --skill agent-evaluation
Clone the repo
git clone --depth 1 https://github.com/ihatesea69/kiro-kit

Made for: Claude Code, Codex.

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 agent-evaluation

README.md
[![agentmods](https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/agent-evaluation.svg)](https://agentmods.dev/skills/ihatesea69/kiro-kit/agent-evaluation)
Your own site
<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/agent-evaluation"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/agent-evaluation.svg" alt="Measured on agentmods" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,170 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00061 $0.01170
Opus 5 $0.00030 $0.00585
Sonnet 5 $0.00012 $0.00234
Haiku 4.5 $0.00006 $0.00117

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

Security

Grade A, and why

agent-evaluation 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 4d 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.

presets/ai-engineer/skills/agent-evaluation/SKILL.md · 128 lines

How it starts

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

Agent Evaluation

Activate this skill when building or fixing the harness that decides whether an agent change is safe to ship.

When to Use

  • Standing up an eval harness for a new agent
  • Wiring an eval job as a CI merge gate
  • Configuring a Bedrock evaluation job
  • Diagnosing a quality regression, or building online drift alarms

Structure

evals/
  golden/
    support.jsonl          # {id, input, expected_tools, expected_facts, rubric}
    adversarial.jsonl      # injection, out-of-scope, unanswerable, PII-bait
  runners/
    run_offline.py         # execute the golden set, emit results.json
    judge.py               # LLM-as-a-Judge with a pinned model + rubric
  thresholds.yaml          # gate config — the only place numbers live
  reports/

Golden Sets

  • 50–200 cases minimum before a pass rate means anything; below that a two-case swing is noise.
  • Mine cases from production transcripts, not imagination. Every incident adds a case — that is what stops the same regression twice.
  • Stratify by intent, difficulty, and known failure mode, and report per stratum. Aggregate scores hide the regression that matters.
  • Always include: prompt-injection attempts, out-of-scope questions, questions the corpus cannot answer (correct response is a refusal), and PII-bait.
  • Version the set with the code; never change the set and the system in one commit.

Deterministic Checks First

Anything checkable in code is checked in code — faster, cheaper, and not itself a model that can drift:

assert result.tools_called == case["expected_tools"]        # routing
assert Schema.model_validate(result.output)                 # structure
assert all(c.source_id in result.retrieved_ids
           for c in result.citations)                       # citations are real
assert result.latency_p95 < budget
assert result.tokens_total < budget
assert result.guardrail_triggered == case["expect_guardrail"]

Tool-selection accuracy is the highest-signal cheap metric in an agent system. Most "the agent gave a bad answer" reports are "the agent called the wrong tool".

Read the full file on GitHub · 128 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. 4d ago First seen · 128 lines · 61 tokens per session scan A e40582e6c82d

Subscribe to this mod's changes

agent-evaluation is a skill published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 19d ago), licensed MIT. It adds 61 tokens to every session and 1,170 once invoked, about $0.0003 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-09-03.

Related

Other skills, from other repositories

e2e

Generate and run Playwright E2E tests traced to spec.md acceptance criteria, with an optional accessibility audit. Use when saying "e2e tests" or "a11y audit".

anton-abyzov/specweave · 38 tokens

tdd-cycle

Execute full TDD red-green-refactor cycle with validation gates. Use when saying "TDD cycle", "test-driven development", or "full TDD workflow".

anton-abyzov/specweave · 33 tokens

genie-orca-review

Independent, read-only review of a group, a wish, or a PR on Orca — SHIP / FIX-FIRST / BLOCKED with severity-tagged findings. Council and retro are this skill with a different input.

automagik-dev/genie · 50 tokens

argot-check

Score your working changes with argot — flag code foreign to this repo's own patterns (unfamiliar dependencies, APIs, constructs), functions the repo already has, code filed in the wrong place, imports that break the repo's layering, and tests weakened, disabled, or deleted alongside a production change — before…

get-tmonier/argot · 110 tokens

ralphctl-test-driven-development

Execute-phase skill — write the failing test before the code that makes it pass; for bug fixes, this is the reproduction test itself. Use for any logic change, bug fix, or behavioural modification; for the full root-cause triage pipeline around an unexpected failure, see ralphctl-debugging-and-error-recovery.

lukas-grigis/ralphctl · 72 tokens

qamap-pr-qa

Local zero-LLM PR QA workflow. Use when an agent is preparing, updating, finalizing, or reviewing a pull request, asks what the PR should test, or needs commit-backed change intent, affected behavior, QA scenarios, evidence, validation commands, optional automation drafts, and manifest repair guidance.

IvoryCanvas/QAMap · 67 tokens