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 jeremylongworth-source/AgentSkills --skill scenario-test-authoringgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/scenario-test-authoring)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/scenario-test-authoring"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/scenario-test-authoring/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/jeremylongworth-source/agentskills/scenario-test-authoring"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/scenario-test-authoring.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.00050 | $0.00326 |
| Opus 5 | $0.00025 | $0.00163 |
| Sonnet 5 | $0.00010 | $0.00065 |
| Haiku 4.5 | $0.00005 | $0.00033 |
Grade A, and why
scenario-test-authoring 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 7d 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
Scenario Test Authoring
Core Workflow
- Identify the user job, target artifact, and skill or bundle that should route for the request.
- Write a realistic prompt that includes enough context to trigger the right skills without naming the expected answer.
- List expected routing using exact skill folder names.
- Add the scenario file under
tests/scenarios/and the matching key intests/expected-routing.yaml. - Include high-risk review or approval expectations in the prompt when the scenario touches customers, production, finance, legal, security, or policy.
- Run validation after adding or changing route scenarios.
Safety Rules
- Do not include private customer, employee, credential, or production data in committed scenarios.
- Do not write scenarios that require live systems or private connectors.
- Do not make routing depend on a host-specific command unless the scenario is explicitly host-specific.
Deliverable Shape
For scenario work, provide:
- Scenario name and user prompt
- Expected routing list
- Future or current bundle
- Acceptance checks
- Risk and review notes
- Files updated
- Validation run
References
- Read
references/scenario-test-authoring-checklist.mdwhen creating or reviewing route scenarios.
What ships with it
2 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.
- 7d ago First seen · 46 lines · 50 tokens per session scan A 44f9d2eab7eb
scenario-test-authoring is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 8d ago), licensed MIT. It adds 50 tokens to every session and 326 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
tester
Run end-to-end web quality audits with Playwright and Lighthouse using existing project scripts first. Use when the user says /tester, e2e test, smoke test, Playwright audit, Lighthouse audit, performance audit, accessibility audit, dark mode audit, mobile audit, or asks for 100/100 Lighthouse improvement guidance.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.
mcore-testing
Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.
i4h-catheter-navigation-render-drr
Render a single DRR fluoroscopy frame from a CT cache or synthetic phantom. Use when asked to render DRR, generate a fluoro image, or smoke-test the Slang renderer.