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/summerengine/summer-engine-agent/skill-testnpx skills add SummerEngine/summer-engine-agent --skill skill-testgit clone --depth 1 https://github.com/SummerEngine/summer-engine-agentWrote 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/summerengine/summer-engine-agent/skill-test)<a href="https://agentmods.dev/skills/summerengine/summer-engine-agent/skill-test"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/skill-test.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.1 | $0.00054 | $0.01030 |
| Opus 5 | $0.00027 | $0.00515 |
| Sonnet 5 | $0.00011 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
skill-test 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- skill-test — 94% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skill-test — Validate a Summer Skill
Three modes. Pick by the user's intent.
Mode: static — Structural lint (default for "test this skill")
For a single skill at skills/<category>/<name>/, run these checks:
- Frontmatter completeness.
name,description,license,compatibility,categorypresent.namematches the directory name. - SKILL.md length. ≤ 500 lines. (Progressive disclosure rule from Anthropic spec.)
- MCP-preferred + file-edit-fallback. If the skill mutates scenes or resources, body must show both:
- At least one
summer_*MCP tool example. - At least one file-edit fallback block (e.g., raw
.tscnsnippet) OR an explicit "no fallback for this — Summer MCP required" note.
- At least one
- Collaborative protocol. If the skill triggers user-visible writes, body must contain at least one of:
May I,I'm about to,Continue?,OK?,Proceed?. Skills that only inspect/read are exempt. - Template-id resolved. If the skill's frontmatter declares
template-id: <id>, that id must exist in../../../references/template-registry.md. - Tests/spec.md present. Every skill in a non-
_metacategory must havetests/spec.mdwith at least one## Caseheading. - Relative links resolve. Every
](../references/...),](../../references/...),](./references/...), and](./examples/...)link must point at an existing file (FAIL if broken). Forward references in## See alsoto other SKILL.md files (e.g.,[design-mechanic](../../gameplay-mechanics/design-mechanic/SKILL.md)) are allowed to dangle and only WARN if the target is missing — the catalog evolves and skills should be free to point at planned skills.
Output:
skill: <category>/<name>
PASS (1) frontmatter complete
PASS (2) length 217 / 500 lines
FAIL (3) no MCP-preferred example found in body
PASS (4) collaborative protocol present
PASS (5) template-id resolved
PASS (6) tests/spec.md exists
PASS (7) all relative links resolve
6 PASS / 1 FAIL — fix item 3 before commit.
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 · 87 lines · 54 tokens per session scan A 48aec2e307f3
skill-test is a skill published in the GitHub repository SummerEngine/summer-engine-agent (57 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,030 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.
Other skills, from other repositories
hearth-playtest
Let the engine hunt bugs for you — bot playtesting via hearth sweep. Seeded bot policies (mash/idle/wander/seek) play a scene headlessly across many seeds and report softlocks, crashes, stuck states, and unmet objectives as a compact evidence report; objectives double as executable acceptance criteria; a failing seed…
tests-run
Execute Unity tests (EditMode or PlayMode) and return per-test results. Supports filtering by test assembly, namespace, class, and method. Refreshes the AssetDatabase first; defers execution across domain reloads if scripts changed. Precondition: every open scene must be saved — dirty scenes abort the run.
playwright-cli
官方Microsoft Playwright CLI网页自动化工具，支持所有主流浏览器的无头/有头自动化操作，包括页面导航、元素交互、截图、录制、测试等功能。当用户提到网页自动化、浏览器操作、爬虫、截图、录制用户操作、E2E测试时触发。.
ccg-workflow
How to run a non-trivial change end to end with the CCG role tools (ccganalyze / ccgdesign / ccgbuild / ccgdebug / ccgoptimize / ccgreview / ccgtest) and the verify- quality gates. Use when a task is a whole feature, a refactor, a bug whose cause is not yet known, or any change large enough that one straight-through…
config-evals
Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it…
self-evolve
Capture reusable patterns from a finished project and lift them into framework-level priors (contracts, modules, skeletons) that future projects inherit. Run only when the user explicitly requests self-evolution; the orchestrator executes the workflow.