Borrowing it
Nothing to install: this file belongs to aziontech/webkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aziontech/webkit/main/.claude/commands/regen-baselines.mdgit clone --depth 1 https://github.com/aziontech/webkitWrote 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/commands/aziontech/webkit/regen-baselines)<a href="https://agentmods.dev/commands/aziontech/webkit/regen-baselines"><img src="https://agentmods.dev/badge/commands/aziontech/webkit/regen-baselines/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/commands/aziontech/webkit/regen-baselines"><img src="https://agentmods.dev/badge/commands/aziontech/webkit/regen-baselines.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.00000 | $0.00463 |
| Opus 5.5 | $0.00000 | $0.00185 |
| Sonnet 5.5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
regen-baselines 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 2mo 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
/regen-baselines <branch | pr-number | pr-url> [modes]
Regenerate the Linux visual baselines for a PR branch in CI and land them on the
branch. Never generate baselines locally — macOS rendering does not match the linux/
snapshots the PR visual gate (governance.yml → test:visual:ci) compares against.
Run the regen-baselines skill (.claude/skills/regen-baselines/SKILL.md). It:
- Resolves the branch (from the PR number/URL when given) and confirms the state to
snapshot — e.g. the
mainmerge/rebase — is already pushed to origin. - Triggers
Storybook Regenerate Baseline(.github/workflows/app-storybook-generate-baseline.yml) withupdate_baselines=true, optionally narrowing to amodessubset. - Waits for the run (~5 min with warm caches) and downloads the
visual-baselines-linuxartifact into a fresh temp dir. - Mirrors it into
apps/storybook/.storybook/test-visual/__image_snapshots__/linux/withrsync -a --delete, so deletions of stale snapshots propagate. - Reviews the diff scope — every changed story must be explainable by the branch's changes; unexplained stories stop the flow.
- Commits only the snapshots folder (
test(storybook): regenerate linux baselines …) and pushes, updating the PR.
modes is a comma-separated subset of the matrix in
apps/storybook/.storybook/visual-modes.js (e.g. light-desktop,dark-mobile);
empty = the full {dark,light} × {desktop,tablet,mobile} cross product. The
dark-desktop snapshot is the historical unsuffixed <story>.png.
Conflict recovery: when main and the branch both regenerated the same snapshots,
finish the merge/rebase first (any side of a conflicted PNG is fine — it is about to be
overwritten), push, then run this flow so the committed baselines come from the merged
tree.
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.
- 2mo ago First seen · 32 lines · 0 tokens per session scan A 8b464351abca
regen-baselines is a command published in the GitHub repository aziontech/webkit (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 463 tokens. 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 commands, from other repositories
implement-feature
Implement an approved feature plan with benefit-based placement, TDD, revision-bound evidence, and PR-ready output.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
verify
Run verification commands and confirm output before making success claims. Use before committing, creating PRs, or claiming work is complete. Evidence before assertions, ALWAYS.