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 Geeksfino/openskills --skill openskills-e2e-test-runbookgit clone --depth 1 https://github.com/Geeksfino/openskillsWrote 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/geeksfino/openskills/openskills-e2e-test-runbook)<a href="https://agentmods.dev/skills/geeksfino/openskills/openskills-e2e-test-runbook"><img src="https://agentmods.dev/badge/skills/geeksfino/openskills/openskills-e2e-test-runbook.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00227 |
| Opus 5 | $0.00018 | $0.00113 |
| Sonnet 5 | $0.00007 | $0.00045 |
| Haiku 4.5 | $0.00004 | $0.00023 |
Grade A, and why
openskills-e2e-test-runbook 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 8d 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
OpenSkills E2E Test Runbook
Use this skill for confidence checks before merging runtime, tooling, or example-agent changes.
Test Layers
- Runtime regression tests
- Sandbox-focused tests
- Example-agent behavior checks
- Optional binding smoke tests
Baseline Commands
cargo test -p openskills-runtime
Example-agent checks (from example directories):
npm install
npm start "What skills are available?"
npm start "Create a new skill called 'note-taker'."
E2E Expectations
- Skills discover successfully.
- Skill activation occurs for matching prompts.
- Tool calls align with intent (activation, file reads/writes, script runs).
- No unexpected sandbox failures.
Reporting Format
- What was run
- What passed
- What failed
- Repro command for each failure
- Suggested next fix
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.
- 8d ago First seen · 45 lines · 37 tokens per session scan A 4fb79bc2c3c4
openskills-e2e-test-runbook is a skill published in the GitHub repository Geeksfino/openskills (71 stars, last pushed 10d ago), licensed Apache-2.0. It adds 37 tokens to every session and 227 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
verify
How to run and drive this app to verify UI/server changes at runtime.
web-frontend-tester
Run frontend functional, accessibility, visual, and performance test planning with structured reports.
qa-react
React testing skill with React Testing Library, Vitest, MSW, and Playwright. Use when writing or running React frontend tests.
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
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.