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/yarlson/yarstack/critical-journey-documentnpx skills add yarlson/yarstack --skill critical-journey-documentgit clone --depth 1 https://github.com/yarlson/yarstackWrote 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/yarlson/yarstack/critical-journey-document)<a href="https://agentmods.dev/skills/yarlson/yarstack/critical-journey-document"><img src="https://agentmods.dev/badge/skills/yarlson/yarstack/critical-journey-document.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.00046 | $0.00340 |
| Opus 5 | $0.00023 | $0.00170 |
| Sonnet 5 | $0.00009 | $0.00068 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
critical-journey-document 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 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.
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
Critical Journey Documentation
Create one canonical journey record in the repository's established product-documentation location.
Workflow
- Confirm what makes the journey critical, its actor, goal, trigger, scope, owner, risk, and canonical document location.
- Inspect existing requirements, code, contracts, tests, telemetry, and documentation; reuse repository identifiers and terminology.
- Split multiple actors or goals into separate records only when independently useful.
- Document the ordered journey, decisions, state changes, success, meaningful failures, recovery, ownership, and evidence links.
- Add acceptance, telemetry, blueprint, portfolio, coverage, or story-map sections only when a named consumer or delivery gate requires them.
- Record unresolved facts only when the task permits them and names the decision owner and resolution condition.
- Use
text-improveon the completed record without changing agreed contracts, identifiers, or domain terms.
Acceptance sections describe product acceptance; test-design owns executable tests. Telemetry sections record agreed contracts rather than inventing events. repo-context-document owns implemented-system flows under docs/context/; rollout-readiness-review owns deployment readiness; spec-update owns semantic decisions.
Do not create a parallel canonical document, mandatory identifier system, speculative telemetry, or an artifact suite by default.
Finish when the record has evidence links, named ownership, explicit unknowns, and only sections with current consumers.
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 · 25 lines · 46 tokens per session scan A f28fc3df726f
critical-journey-document is a skill published in the GitHub repository yarlson/yarstack (3 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 340 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-31.
Other skills, from other repositories
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…
release-cli
Release a new version of the tokenmaxxing CLI to npm. Use when explicitly asked to release or publish @851-labs/tokenmaxxing, including checking main, bumping apps/cli/package.json, updating CHANGELOG.md, committing, tagging cli-vX.Y.Z, pushing, monitoring generated native package publishing, and smoke testing the…
ship-mobile-app
Build, change, debug, and prepare production mobile apps across domain meaning, local and server state, lifecycle, platform, and release boundaries. Use for non-trivial Flutter, React Native, iOS, or Android work involving persistence, sync, auth, offline behavior, notifications, permissions, native integrations…
verify-regression-tests
Verify that a regression test actually detects the defect it claims to guard against. Use after adding or reviewing a bug-fix guard, reproducing the original failure after a fix, or investigating a suspiciously green regression test. Do not use for general TDD, broad test-suite audits, mutation-score optimization…
fable-mode
MANDATORY before diagnosing any bug, debugging any failure, reviewing code, or making a non-trivial change — invoke FIRST, before reading code or proposing a cause; do not skip because the task "looks simple". Five-gate rigor protocol (scope, evidence, attack, verify, report) with per-task playbooks and tripwires.…
repository-bootstrap
Audit and establish or upgrade the canonical repository governance baseline. Use only when explicitly asked to bootstrap, standardize, or upgrade a repository; do not use for feature development or source-code restructuring.