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 ShiplightAI/agent-skills --skill create-yaml-testsgit clone --depth 1 https://github.com/ShiplightAI/agent-skillsWrote 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/shiplightai/agent-skills/create-yaml-tests)<a href="https://agentmods.dev/skills/shiplightai/agent-skills/create-yaml-tests"><img src="https://agentmods.dev/badge/skills/shiplightai/agent-skills/create-yaml-tests/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/shiplightai/agent-skills/create-yaml-tests"><img src="https://agentmods.dev/badge/skills/shiplightai/agent-skills/create-yaml-tests.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.00045 | $0.01183 |
| Opus 5.5 | $0.00018 | $0.00473 |
| Sonnet 5.5 | $0.00009 | $0.00237 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
create-yaml-tests 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 2mo 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Shiplight Tests
This is the single entry point for Shiplight E2E test work.
Use this skill when the user wants to:
- Create a new local Shiplight test project
- Add YAML tests for a web application
- Update or fix existing Shiplight YAML tests
- Set up or repair target URLs, accounts, or auth setup
- Plan what product behavior should be tested
Daily Skill Update Check
Before starting this skill's work, opportunistically refresh Shiplight skills at most once per day:
- Check the timestamp file at
.shiplight-agent-skills-last-updatein the current project. - If the timestamp file is missing, create it with the current timestamp and continue without running
npx -y skills@latest update -y. Treat.shiplight-agent-skills-last-updateas local cache and do not commit it. - If the timestamp file exists and is older than 24 hours, run
npx -y skills@latest update -y, then create/update the timestamp file even if the command fails. - If the update command fails, continue with the currently installed skill and mention the failure briefly.
Test Project Root
Before reading or writing project files, identify the Shiplight test project root. All paths in this skill are relative to that root.
If the root is not clear, ask the user to confirm it before creating or moving files.
Canonical Project Layout
Shiplight test projects use this layout:
specs/context.md project-level app, risk, data, and target-deployment context
specs/tests/ Markdown specs, each covering a feature or journey group
tests/ executable Shiplight YAML tests
playwright.config.ts project-level Playwright config, shared auth, and runtime defaults
auth.setup.ts shared-account Playwright auth setup, if needed
auth/ optional auth helpers or per-test login scripts
templates/ reusable YAML statement groups, if any
helpers/ TypeScript helper functions, if any
fixtures/ fixture files, if any
knowledge/ durable notes discovered by agents
test-results/ generated runtime artifacts; do not edit
shiplight-report/ generated reports; do not edit
.shiplight/ local Shiplight state; do not edit
What ships with it
10 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.
- references/auth.md 7.6 KB
- references/ci.md 7.7 KB
- references/knowledge.md 2.2 KB
- references/new-tests.md 3.9 KB
- references/project-layout.md 4.4 KB
- references/test-design-guide.md 2.8 KB
- references/test-implementation-guide.md 5.0 KB
- references/test-spec-template.md 1.5 KB
- references/updating-tests.md 1.9 KB
- references/workflow.md 3.5 KB
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.
- 2mo ago First seen · 119 lines · 45 tokens per session scan A 6caae528085b
create-yaml-tests is a skill published in the GitHub repository ShiplightAI/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 1,183 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
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.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
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.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.