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 thkt/dotclaude --skill use-workflow-pageshotgit clone --depth 1 https://github.com/thkt/dotclaudeWrote 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/thkt/dotclaude/use-workflow-pageshot)<a href="https://agentmods.dev/skills/thkt/dotclaude/use-workflow-pageshot"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/use-workflow-pageshot/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/thkt/dotclaude/use-workflow-pageshot"><img src="https://agentmods.dev/badge/skills/thkt/dotclaude/use-workflow-pageshot.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.00078 | $0.00884 |
| Opus 5.5 | $0.00031 | $0.00354 |
| Sonnet 5.5 | $0.00016 | $0.00177 |
| Haiku 4.5 | $0.00008 | $0.00088 |
Grade A, and why
use-workflow-pageshot 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
use-workflow-pageshot
入力
PR 本文は /pr から文字列として渡される。下表のいずれかが欠落していれば、mode=failed reason=<欠落フィールド名> を返し、判断は /pr に任せる。
| フィールド | ソース |
|---|---|
| Preview URL | PR 本文の冒頭にある Preview URL: <URL> 行 |
| Steps | PR 本文の ## How to Test セクション配下の番号付きリスト |
ブラウザ engine
すべての agent-browser 呼び出しに --session pageshot --engine chrome を付ける。既定の lightpanda は screenshot でプレースホルダー PNG を返す。
モード選択
| Steps の数 | モード | 成果物 |
|---|---|---|
| 1 | screenshot | step-01.png |
| 2+ | video | capture.mp4 |
実行
| ステップ | アクション |
|---|---|
| 1 | 出力ディレクトリを作成。.claude/workspace/pageshot/$(date +%Y%m%d-%H%M%S)/ |
| 2 | agent-browser open {Preview URL} |
| 3 | モードに応じて Screenshot Flow または Video Flow を実行 |
| 4 | 成果物の絶対パスを stdout に出力 |
Screenshot Flow (1 step)
| # | コマンド |
|---|---|
| 1 | agent-browser snapshot でアクセシビリティツリーを取得 |
| 2 | step に操作が含まれていれば agent-browser {click/type/fill/...} を実行 |
| 3 | agent-browser screenshot --full {outdir}/step-01.png |
Video Flow (2+ steps)
step 間に agent-browser wait 500 を挟む。各操作の前に snapshot を実行して要素を特定する。
| # | コマンド |
|---|---|
| 1 | agent-browser record start {outdir}/capture.webm |
| 2 | 各 step について順に snapshot してから操作を実行 |
| 3 | agent-browser record stop |
| 4 | ffmpeg -i {outdir}/capture.webm -vcodec libx264 {outdir}/capture.mp4 |
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.
- 1mo ago Changed · -1 tokens per session 3ffa7dcc559e
- 1mo ago First seen · 70 lines · 79 tokens per session scan A eed1fc362530
use-workflow-pageshot is a skill published in the GitHub repository thkt/dotclaude (12 stars, last pushed 25d ago), licensed MIT. It adds 78 tokens to every session and 884 once invoked, about $0.0003 per session on Opus 5.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.
Other skills, from other repositories
qa-testing
Run QA testing on a page, feature, or full site at one of three depth tiers (smoke, standard, full). Use this skill whenever the user asks to QA a page or site, run a smoke test after a deploy, verify a page before launch, or run a regression sweep. Triggers on QA, QA sweep, smoke test, regression test, post-deploy…
bug-bash
Programmatic bug bashing, ingest a prescribed test plan (Notion, markdown, pasted spec), drive a real running system (browser via Chrome DevTools / Playwright MCP, backend via API tools when relevant), run every prescribed case with evidence, then do exploratory passes (viewports, multi-actor flows, codebase-driven…
implementation-review
Pre-commit quality gate. Invoke before every git commit, after /flagrare:staleness-audit. Seven checks, plan gaps, use-case coverage gaps, missing test scenarios, test philosophy violations (Kent Dodds Testing Trophy), SOLID violations, Clean Code violations, and security vulnerabilities. Each check is delegated to a…
wrap-up
Post-implementation quality gate. Runs automated checks (tests, lint, types), invokes /flagrare:implementation-review for the seven-check parallel review, culls every code comment in the diff that is not a trap-preventer, then performs additional SOLID and Clean Code review on any findings not covered. Use when the…
e2e-testing
Playwright E2E testing patterns — Page Object Model, configuration, CI/CD integration, artifact management, flaky test strategies, PLUS the decision-time patterns that come before the first test is written (black-box helper scripts, static-vs-dynamic routing, multi-server orchestration, reconnaissance-then-action…
post-deploy-qa
A post-deployment quality check for testing a live application after it has been released.