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 agentmods add skills/microsoft/agentic-journeys/journey-templatenpx skills add microsoft/agentic-journeys --skill journey-templategit 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-template)<a href="https://agentmods.dev/skills/microsoft/agentic-journeys/journey-template"><img src="https://agentmods.dev/badge/skills/microsoft/agentic-journeys/journey-template.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 | $0.00153 | $0.09080 |
| Opus 5 | $0.00077 | $0.04540 |
| Sonnet 5 | $0.00031 | $0.01816 |
| Haiku 4.5 | $0.00015 | $0.00908 |
Grade A, and why
journey-template scanned grade A with 2 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
11. **Verification Checklist** — curl / az commands to confirm deployment Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
For example, n8n's `WEBHOOK_URL` depends on the Container App URL. The CommonJS `.js` hook resolves paths with `__dirname`, reads outputs with `azd env get-value`, and invokes Azure CLI with argument arrays. It must not This is a copy
100% identical to journey-template — 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 — 836 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journey Template Skill
Generate a complete agentic journey from a user's app idea. A journey is a hands-on learning experience where developers use GitHub Copilot (CLI, app, or IDE) to build and deploy an app to Azure.
Curriculum packaging (required)
Every journey README must include:
- No journey-sequence or learning-path numbering such as "Journey 2 of 5" — journeys are self-contained. Numbered phases and steps inside one journey are encouraged when they clarify the flow.
- Honest first-run time + cost if left running + same-day teardown
- Done when checklist with concrete manual verification steps
- Full-stack: one-line default stack at the first generate prompt (not a defaults table); put stack details in PLAN.md
- Plugin commands: only
microsoft/azure-skills/azure@azure-skills - What's Next uses plain links to related journeys, not prescribed-path or completion language
- OSS: shared deploy recipe (location, secrets, probes, resolve issues, issues.md)
- An isolated-workspace setup prompt that copies the journey,
.github/agents,.github/skills,.github/scripts, anddocswithout modifying the source repository - A prerequisite table, concrete local/Azure acceptance criteria, and a reusable exact-error recovery prompt
- A prompt that creates every generated verifier or diagnostic script before the README tells the learner to run it
- A read-only pre-deployment review with READY/NOT READY, PASS/FAIL evidence, and fail-closed blockers
- Agent-led azd environment preparation, followed by the learner running the consequential
azd upcommand - No checked-in journey
issues.md: prompts create it only in the isolated learner workspace when a real issue occurs
Update root README.md learning path + journey table when adding a journey.
Journey Types
| Dimension | Full-Stack (e.g. AIMarket) | OSS Deployment (e.g. n8n, Grafana, Superset) |
|---|---|---|
| What the learner does | Builds an app from scratch with GitHub Copilot | Deploys an existing OSS app via @oss-to-azure-deployer agent |
| Files generated | README.md + PLAN.md | README.md + app-specific skill in .github/skills/ |
| README structure | "The Journey" with 3-5 phases (adapt to app complexity) | "Deploy with the Agent" with 3 steps (Setup → Deploy → Verify) |
| Images | 4-6 (one per phase boundary) | 2 (hero + deployment) |
| Unique sections | "The Spec", "How Agentic AI is Used", one-line default stack at first prompt | "Configuration Reference", "Key Learnings", skip rules if expensive |
| Compute target | Container Apps, App Service, Functions, Static Web Apps, AKS | Container Apps, AKS, App Service |
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.
- 5d ago First seen · 836 lines · 153 tokens per session scan A a087f3e755e7
journey-template is a skill published in the GitHub repository microsoft/agentic-journeys (5 stars, last pushed 26d ago), licensed MIT. It adds 153 tokens to every session and 9,080 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). It is 100% identical to journey-template, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
best-practices
Searchable knowledge base of 152+ programming best practices across 30+ languages and frameworks. BM25-powered search over curated resources from industry leaders (Google, Airbnb, Uber, Mozilla, Shopify, OWASP).