github-azure-agentic-journeys: Skill for Claude Code

.github/skills/journey-runner/SKILL.md

journey-runner is a skill for Claude Code, Codex from DanWahlin/github-azure-agentic-journeys. It costs 113 tokens per session (3,528 once invoked), scanned A, original, MIT.

An end-to-end runner for testing a learner journey: a sequence of prompts or tasks completed by an agent from start to finish.

In plain words
What is it for?
Validate journey prompts, test supported technology stacks, deploy journey projects to Azure, verify them, and clean up resources owned by the run.
Why use it?
It catches problems that unit tests may miss by building, deploying to Azure, making real requests, taking screenshots, and checking the result in an isolated workspace.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is DanWahlin/github-azure-agentic-journeys's own configuration. It tells Claude Code and Codex how to work on github-azure-agentic-journeys itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything github-azure-agentic-journeys configures →

Reuse

Borrowing it

Nothing to install: this file belongs to DanWahlin/github-azure-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.

Copy the file
curl -O https://raw.githubusercontent.com/DanWahlin/github-azure-agentic-journeys/main/.github/skills/journey-runner/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/DanWahlin/github-azure-agentic-journeys

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for journey-runner

README.md
[![agentmods](https://agentmods.dev/badge/skills/danwahlin/github-azure-agentic-journeys/journey-runner/github.svg)](https://agentmods.dev/skills/danwahlin/github-azure-agentic-journeys/journey-runner)
Your own site
<a href="https://agentmods.dev/skills/danwahlin/github-azure-agentic-journeys/journey-runner"><img src="https://agentmods.dev/badge/skills/danwahlin/github-azure-agentic-journeys/journey-runner/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.

agentmods 80×15 button for journey-runner

Your own site · 80×15
<a href="https://agentmods.dev/skills/danwahlin/github-azure-agentic-journeys/journey-runner"><img src="https://agentmods.dev/badge/skills/danwahlin/github-azure-agentic-journeys/journey-runner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 113 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,528 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 236
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 239
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00113 $0.03528
Opus 5 $0.00056 $0.01764
Sonnet 5 $0.00023 $0.00706
Haiku 4.5 $0.00011 $0.00353

Measured 9d ago against content hash 705f4a4671fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

journey-runner 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 9d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/capture-screenshot.mjs, scripts/check-prerequisites.mjs, scripts/run-copilot-prompt.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.github/skills/journey-runner/SKILL.md · 302 lines

How it starts

The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Journey Runner Skill

Run a journey like a learner would, but with strict preflight, isolated state, evidence-backed verification, and scoped cleanup. The workflow must work on Windows, Mac, and Linux.

Required Runner Tools

The runner itself requires:

  • Node.js LTS or later
  • Azure CLI
  • Azure Developer CLI (azd) 1.28.0 or later
  • GitHub Copilot CLI

Screenshot runs additionally require the local Playwright package and bundled Chromium under scripts/. Installation options for all operating systems are in ../../../docs/tool-installation.md.

Do not install system tools during a run. Report the missing tool, its install link, and the validation command, then stop before generating code or creating Azure resources. Project-local npm ci for the checked-in runner helpers is allowed only during explicit runner setup, not as a surprise halfway through a journey.

Inputs and Defaults

Inputs:

  1. Journey path, such as journeys/smart-todo/
  2. Stack choice when the journey supports multiple stacks
  3. Azure subscription for deployment runs
  4. Cleanup policy: after-verification or leave-running

Defaults:

Behavior Default
Deploy to Azure Yes, when the journey contains a deployment phase
Cleanup after-verification
Stack Use the only option; ask before starting when multiple materially different stacks exist
Verification failure Record the failure, attempt one evidence-based repair, then stop that phase if it still fails
Output Concise phase summary plus artifact paths and actual command results

Only use leave-running when the user explicitly requests it.

Step 0: Parse the Journey

Read the journey's README.md, PLAN.md when present, and every associated journey skill. Extract:

  • Journey type and phases
  • Prompts to send to Copilot
  • Commands and generated scripts
  • Required and optional host tools
  • Local ports
  • Deployment outputs
  • Verification criteria
  • Platform gates such as Xcode

Read the full file on GitHub · 302 lines

Files

What ships with it

6 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.

Changes

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.

  1. 9d ago First seen · 302 lines · 113 tokens per session scan A 705f4a4671fd

Subscribe to this mod's changes

journey-runner is a skill published in the GitHub repository DanWahlin/github-azure-agentic-journeys (37 stars, last pushed 1mo ago), licensed MIT. It adds 113 tokens to every session and 3,528 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

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.

wshobson/agents · 39 tokens

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.

wshobson/agents · 51 tokens

azure-microsoft-playwright-testing-ts

Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.

microsoft/skills · 53 tokens

pod-e2e

ONLY for developing Kiro Crew itself -- if the project you are working on is anything else, ignore this skill: it drives Kiro Crew's own pod tooling, which does not exist in another repository. Runs end-to-end tests (backend API + frontend Playwright) for a Kiro Crew feature worktree against an ISOLATED throwaway pod…

kirodotdev/KiroCrew · 147 tokens

android-emulator

Verify and debug native, React Native, Expo, or Flutter apps on an Android Emulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an Android virtual device.

callstack/agent-device · 65 tokens

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.

callstack/agent-device · 55 tokens