evals

A plugin for connecting a code repository to Tessary's evaluation service, which analyzes whether LLM calls follow expected behavior.

In plain words
What is it for?
It helps configure trace collection over OTLP, label LLM call sites, inspect evaluation results, investigate failing traces, and maintain per-call-site procedure files.
Why use it?
It brings trace data, call-site labels, graders, failing cases, and root-cause reports into the coding-agent workflow so problems can be investigated in context.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add tessaryai/plugins
agentmods
npx agentmods add plugins/tessaryai/plugins/evals
Clone the repo
git clone --depth 1 https://github.com/tessaryai/plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

evals 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 yesterday.

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/evals/.claude-plugin/plugin.json · 20 lines

What it actually says

{
  "name": "evals",
  "description": "Connect your repo to evals.tessary.ai and work with your evals from the coding agent \u2014 wire trace ingestion over OTLP, tag your call sites, assess graders, query failing traces, read the cases and root-cause reports the platform opens, and author per-call-site SOP-conformance files (derive from the code, reconcile on change, lint locally). The platform's observer authors and maintains your eval bundle from there.",
  "version": "0.27.1",
  "author": {
    "name": "Tessary AI"
  },
  "homepage": "https://evals.tessary.ai",
  "repository": "https://github.com/tessaryai/plugins",
  "license": "MIT",
  "keywords": [
    "evals",
    "llm",
    "graders",
    "observability",
    "mcp",
    "coding-agent"
  ]
}
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. yesterday First seen · 20 lines scan A 0184ab4b1530

Subscribe to this mod's changes

evals is a plugin published in the GitHub repository tessaryai/plugins (3 stars, last pushed 14d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.