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 skills add wyattowalsh/agents --skill skill-eval-scaffoldergit clone --depth 1 https://github.com/wyattowalsh/agentsWrote 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/wyattowalsh/agents/skill-eval-scaffolder)<a href="https://agentmods.dev/skills/wyattowalsh/agents/skill-eval-scaffolder"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/skill-eval-scaffolder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wyattowalsh/agents/skill-eval-scaffolder"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/skill-eval-scaffolder.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00037 | $0.00447 |
| Opus 5.5 | $0.00015 | $0.00179 |
| Sonnet 5.5 | $0.00007 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
skill-eval-scaffolder 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 1mo 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.
What it actually says
Skill Eval Scaffolder
Create minimal, schema-valid eval manifests for repository skills.
Scope: Eval scaffolding only. Do not run live behavioral evals unless the maintainer explicitly approves.
Dispatch
| $ARGUMENTS | Action |
|---|---|
<name> |
Preview scaffold for skills/<name>/evals/evals.json |
<name> --apply |
Write scaffold when file is missing or user approved overwrite |
check <name> |
Validate an existing eval manifest |
| Empty | Show usage gallery and manifest schema summary |
Workflow
- Confirm
skills/<name>/SKILL.mdexists. - Run the bundled scaffold script:
uv run python skills/skill-eval-scaffolder/scripts/scaffold_evals.py <name>
- Add explicit, implicit, and negative-control cases before claiming adequate coverage.
- Validate with the bundled check script.
Manifest Shape
Each evals/evals.json uses:
skill_name— kebab-case directory nameevals— non-empty list of cases withid,prompt,expected_output, optionalfiles,assertions
Validation Contract
uv run python skills/skill-eval-scaffolder/scripts/check.py
Critical Rules
- Never overwrite an existing eval manifest without explicit user approval.
- Include at least one explicit-invocation case in new scaffolds.
- Run
validate_evals.pybefore declaring the scaffold complete. - Route live eval execution to skill-creator
evalmode or maintainer CI workflows. - Keep prompts grounded in the skill dispatch table and NOT-for boundaries.
What ships with it
4 files 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.
- 1mo ago First seen · 61 lines · 37 tokens per session scan A 53ecdb4963e8
skill-eval-scaffolder is a skill published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 447 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.