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 bnayahu/journeycast --skill capturing-journeysgit clone --depth 1 https://github.com/bnayahu/journeycastWrote 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/bnayahu/journeycast/capturing-journeys)<a href="https://agentmods.dev/skills/bnayahu/journeycast/capturing-journeys"><img src="https://agentmods.dev/badge/skills/bnayahu/journeycast/capturing-journeys/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/bnayahu/journeycast/capturing-journeys"><img src="https://agentmods.dev/badge/skills/bnayahu/journeycast/capturing-journeys.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.00046 | $0.00442 |
| Opus 5 | $0.00023 | $0.00221 |
| Sonnet 5 | $0.00009 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
capturing-journeys scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **Confirm the app is running.** Health-check `app.baseUrl` (e.g. `curl -sSf <baseUrl> -o /dev/null`). If unreachable, tell the user to start the app and stop. What it actually says
Capturing journeys
Run the deterministic capture engine over the human-approved journey.yaml.
Paths follow the Output location convention from deriving-journeys: the journey lives at $OUTDIR/journey.yaml (<target-repo>/docs/journeycast/pr-<pr>/journey.yaml) and capture scratch goes under $WORKDIR (out/pr-<pr>/ in the journeycast clone, gitignored). Resolve both from the PR number before running.
Steps
-
Re-validate after edits. Run
node engine/validate.mjs "$OUTDIR/journey.yaml". If it exits non-zero, show the field errors and route the user back to the edit gate. Do not capture an invalid journey. -
Confirm the app is running. Health-check
app.baseUrl(e.g.curl -sSf <baseUrl> -o /dev/null). If unreachable, tell the user to start the app and stop. -
Capture. Run
node engine/capture.mjs --journey "$OUTDIR/journey.yaml" --out "$WORKDIR/capture". This navigates, performs actions, waits, screenshots each step, and resolves callout/zoom bounding boxes. -
Verify assets. Confirm
$WORKDIR/capture/capture-manifest.jsonexists and that each non-title/outro step lists at least oneframes[].paththat exists on disk. -
Handle failures. If capture exits non-zero, it prints a
CaptureErrornaming the failing step id and the attempted selector. Surface that message verbatim, note that partial assets were retained under$WORKDIR/capture, and route the user back to the edit gate to fix the selector or step.
Output
$WORKDIR/capture/capture-manifest.json plus per-step screenshots, ready for rendering.
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 · 27 lines · 46 tokens per session scan A 487b52b71f10
capturing-journeys is a skill published in the GitHub repository bnayahu/journeycast (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 442 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
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…