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/joris887/exosuit/skill-evalnpx skills add joris887/exosuit --skill skill-evalgit clone --depth 1 https://github.com/joris887/exosuitWrote 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.
[](https://agentmods.dev/skills/joris887/exosuit/skill-eval)<a href="https://agentmods.dev/skills/joris887/exosuit/skill-eval"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/skill-eval.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00032 | $0.01537 |
| Opus 5 | $0.00016 | $0.00768 |
| Sonnet 5 | $0.00006 | $0.00307 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
skill-eval 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 3d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-eval
Evaluating skill: $ARGUMENTS
Modes
Parse the first argument to determine mode:
| Mode | Syntax | Purpose |
|---|---|---|
| eval | /skill-eval eval <skill-name> --scenario "<prompt>" |
Test a skill against a known scenario |
| compare | /skill-eval compare <skill-name> --old <path> --new <path> --scenario "<prompt>" |
A/B test two versions of a skill |
| metrics | /skill-eval metrics <skill-name> |
Analyze a skill's evaluation criteria and pressure scenarios |
| baseline | /skill-eval baseline <skill-name> --scenario "<prompt>" |
Capture baseline output for regression detection |
| regression | /skill-eval regression <skill-name> |
Compare current skill against saved baseline |
Mode: eval
Test a skill against a scenario and grade the output against expectations.
Process
- Load the skill — Read
.claude/skills/<skill-name>/SKILL.md - Load evaluation criteria — Read the skill's
## Evaluation Criteriasection (if present in SKILL.md or SKILL_TEMPLATE.md) - Define the scenario — Use the provided
--scenarioor prompt the user for one - Execute mentally — Walk through what Claude would do with this skill loaded, given the scenario prompt. Trace the expected decision points, tool calls, and outputs.
- Grade against criteria — For each evaluation criterion, determine PASS/FAIL with evidence
Output
## Skill Evaluation: <skill-name>
### Scenario
> <the test scenario>
### Expected Behavior
| # | Criterion | Status | Evidence |
|---|-----------|--------|----------|
| 1 | [criterion text] | PASS/FAIL | [why] |
### Hard Gate Compliance
- [ ] All hard gates would be respected
- [ ] Red flags table would prevent shortcuts (if applicable)
### Context Budget
- Estimated SKILL.md tokens: X
- References loaded: [list]
- Total estimated tokens: X
### Verdict: PASS / FAIL / PARTIAL
[Summary of findings]
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 202 lines · 32 tokens per session scan A 8c955efe7197
skill-eval is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 14d ago), licensed MIT. It adds 32 tokens to every session and 1,537 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-31.
Other skills, from other repositories
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
linkedin-post
You take a YouTube video transcript and produce a single LinkedIn post draft.
orchestrator-lanes
Claude Code dev-orchestrator only. File-based multi-lane PM playbook (score, DAG, run-controller, L0/L1/L2, ship). Use when this session IS that agent, or user says info / справка / lane-stack:orchestrator-lanes info. SKIP: Grok, Codex, Kimi, Qwen, AGY, Cursor writer CLIs and any default coding agent — do not load, do…
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
source-command-ccguide-daily
Daily update check — official Anthropic docs diff + guide/CC releases digest.