Borrowing it
Nothing to install: this file belongs to microsoft/agentic-journeys. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/agentic-journeys/main/.github/skills/journey-test-harness/SKILL.mdgit clone --depth 1 https://github.com/microsoft/agentic-journeysWrote 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/microsoft/agentic-journeys/journey-test-harness)<a href="https://agentmods.dev/skills/microsoft/agentic-journeys/journey-test-harness"><img src="https://agentmods.dev/badge/skills/microsoft/agentic-journeys/journey-test-harness.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.00109 | $0.01758 |
| Opus 5 | $0.00055 | $0.00879 |
| Sonnet 5 | $0.00022 | $0.00352 |
| Haiku 4.5 | $0.00011 | $0.00176 |
Grade A, and why
journey-test-harness 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.
This is a copy
100% identical to journey-test-harness — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journey Test Harness
Orchestrate journey-runner across the selected journey directories. The harness must work on Windows, Mac, and Linux and must never delete an Azure environment merely because it appears in azd env list.
Inputs
- Journeys, default
all - Stack, default Node.js/TypeScript for multi-stack journeys
- Deploy, default
true - Location, default
westus - Concurrency, default
1; increase only when quota, local ports, and API limits allow it
Each deployed journey uses cleanup: after-verification unless the user explicitly requests otherwise.
Step 1: Discover Journeys
Use repository file-search APIs or Node.js fs.readdir() to find journeys/*/README.md. Do not use ls | sed, shell globs, or platform-specific path parsing.
For each journey, record:
- Folder name and absolute source path
- Journey type
PLAN.mdpresence- Required and optional tools from the journey prerequisite section
- Estimated cost and time
- Screenshot requirement
Filter only against the discovered folder names. Fail early for an unknown requested journey.
Step 2: Suite Preflight
Load journey-runner and run its cross-platform preflight before creating any workspace or Azure resource.
The union of selected-journey requirements may include:
- Node.js LTS or later
- Azure CLI and valid authentication
azd1.28.0 or later withauth.useAzCliAuth=true- GitHub Copilot CLI
- Node.js LTS or later for hooks, tests, and verifiers
- Azure Functions Core Tools v4, Azurite, and Go-based
sqlcmdfor SmartTodo - The pinned Playwright package and bundled Chromium for web screenshots
- Xcode 16+ only when SmartTodo iOS execution is requested on Mac
Use .github/skills/journey-runner/scripts/check-prerequisites.mjs with the union of required tools. Missing required tools stop the whole suite before provider registration. Do not install system tools during the suite.
Step 3: Azure Preparation
Check Azure CLI and azd authentication separately. Confirm the intended subscription and location.
What ships with it
1 file 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.
- 8d ago First seen · 199 lines · 109 tokens per session scan A 79b99bdcde95
journey-test-harness is a skill published in the GitHub repository microsoft/agentic-journeys (5 stars, last pushed 1mo ago), licensed MIT. It adds 109 tokens to every session and 1,758 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to journey-test-harness, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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.
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.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…