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.
npx agentmods add skills/shihongdev/evalyn/evalyn-setupnpx skills add shihongDev/evalyn --skill evalyn-setupgit clone --depth 1 https://github.com/shihongDev/evalynWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00030 | $0.00698 |
| Opus 5 | $0.00015 | $0.00349 |
| Sonnet 5 | $0.00006 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
evalyn-setup 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
evalyn-setup
Overview
Guide a developer through instrumenting their LLM agent with evalyn so traces are captured for evaluation.
Pre-flight
Check evalyn is installed:
python -m pip show evalyn-sdk 2>/dev/null
If not installed:
pip install evalyn-sdk
Step 1: Detect Agent Framework
Scan the user's agent code for imports to determine the framework:
Supported frameworks (all auto-instrumented - decorator is sufficient):
langchain, langgraph, anthropic, openai, google.generativeai, google.adk, claude_agent_sdk
If no recognized framework: the decorator still works for any Python function, but LLM calls won't have token/cost details.
Step 2: Add the Decorator
Add to the agent's main entry function. The import evalyn_sdk line MUST come before any framework imports (it patches LLM clients via sys.meta_path):
import evalyn_sdk # Must be FIRST import — patches LLM clients for tracing
from evalyn_sdk import eval
@eval(project="<project-name>", version="v1")
def agent_function(query: str) -> str:
# existing agent code
...
Rules:
import evalyn_sdkmust be the very first import in the fileproject: descriptive kebab-case name (e.g., "my-research-agent")version: tracks iterations, start with "v1"- Wrap the outermost function that represents one agent invocation
- Do NOT wrap internal helper functions
- Optional
nameparameter overrides the display name (defaults to function name)
Real example from the codebase:
import evalyn_sdk # First import
from evalyn_sdk import eval
@eval(project="gemini-deep-research-agent", version="v1", name="research_agent")
def run_agent(question: str) -> str:
...
Step 3: Run the Agent
Tell the user to run their agent with at least 3 different inputs to generate traces:
python path/to/agent.py "first test query"
python path/to/agent.py "second different query"
python path/to/agent.py "third varied query"
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.
- 2d ago First seen · 105 lines · 30 tokens per session scan A 0b9cb1d9fd33
evalyn-setup is a skill published in the GitHub repository shihongDev/evalyn (257 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 698 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…