WigAI: Skill for Claude Code

.claude/skills/bmad-checkpoint-preview/SKILL.md

bmad-checkpoint-preview is a skill for Claude Code from fabb/WigAI. It costs 49 tokens per session (283 once invoked), scanned A, original, MIT.

A guided review of a software change that helps a person understand it, focus on important parts, and test it. It can be started with requests such as “checkpoint” or “human review.”

In plain words
What is it for?
Use it to walk through a change, identify areas needing attention, and plan or perform checks before approval.
Why use it?
It helps people review changes efficiently when they need context and practical guidance before deciding whether the change is acceptable.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is fabb/WigAI's own configuration. It tells Claude Code how to work on WigAI itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything WigAI configures →

View source ↗ fabb/WigAI
Reuse

Borrowing it

Nothing to install: this file belongs to fabb/WigAI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/fabb/WigAI/main/.claude/skills/bmad-checkpoint-preview/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/fabb/WigAI

Made for: Claude Code.

Wrote 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.

agentmods badge for bmad-checkpoint-preview

README.md
[![agentmods](https://agentmods.dev/badge/skills/fabb/wigai/bmad-checkpoint-preview/github.svg)](https://agentmods.dev/skills/fabb/wigai/bmad-checkpoint-preview)
Your own site
<a href="https://agentmods.dev/skills/fabb/wigai/bmad-checkpoint-preview"><img src="https://agentmods.dev/badge/skills/fabb/wigai/bmad-checkpoint-preview/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.

agentmods 80×15 button for bmad-checkpoint-preview

Your own site · 80×15
<a href="https://agentmods.dev/skills/fabb/wigai/bmad-checkpoint-preview"><img src="https://agentmods.dev/badge/skills/fabb/wigai/bmad-checkpoint-preview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 283 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.00283
Opus 5.5 $0.00020 $0.00113
Sonnet 5.5 $0.00010 $0.00057
Haiku 4.5 $0.00005 $0.00028

Measured 1mo ago against content hash 46e919d5ba64, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bmad-checkpoint-preview 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/bmad-checkpoint-preview/SKILL.md · 30 lines

What it actually says

Checkpoint Review Workflow

Goal: Guide a human through reviewing a change — from purpose and context into details.

You are assisting the user in reviewing a change.

Global Step Rules (apply to every step)

  • Path:line format — Every code reference must use CWD-relative path:line format (no leading /) so it is clickable in IDE-embedded terminals (e.g., src/auth/middleware.ts:42).
  • Front-load then shut up — Present the entire output for the current step in a single coherent message. Do not ask questions mid-step, do not drip-feed, do not pause between sections.
  • Language — Speak in {communication_language}. Write any file output in {document_output_language}.

INITIALIZATION

Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:

  • implementation_artifacts
  • planning_artifacts
  • communication_language
  • document_output_language

FIRST STEP

Read fully and follow ./step-01-orientation.md to begin.

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 1mo ago First seen · 30 lines · 49 tokens per session scan A 46e919d5ba64

Subscribe to this mod's changes

bmad-checkpoint-preview is a skill published in the GitHub repository fabb/WigAI (62 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 283 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

sumo-qa-implementing-with-tdd

Use after sumo-qa-deciding-approach picks tdd-scaffold, regression-first, or coverage-first-then-refactor — e.g. "write a regression test for this bug" or "scaffold the failing tests first". Walks plan → name-the-risk-and-test-idea → confirm → red → hand off → green → review, one section per turn with confirmation…

sumithr/sumo-qa · 103 tokens

sumo-qa-finishing-qa-work

Use at the end of a QA rollout (after sumo-qa-executing-qa-rollout, or after a manual multi-step QA task) to capture evidence, produce a PR-ready summary, and close the loop. Runs the suite one last time, captures coverage / risk-to-test map / open follow-ups, writes a markdown summary to docs/qa/runs/YYYY-MM-DD- .md…

sumithr/sumo-qa · 102 tokens

sumo-qa-planning-qa-rollout

Use after sumo-qa-deciding-approach routes here, when you have a chunk of QA work (a story, a PR, a strategy phase) that needs to be turned into a written plan of bite-sized, independently-executable tasks before any test code is written. Produces docs/qa/plans/YYYY-MM-DD- .md ready for subagent dispatch via…

sumithr/sumo-qa · 101 tokens

live-audit

Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…

Grinv/steam-games-mcp · 83 tokens

sumo-qa-preparing-for-work

Use after sumo-qa-deciding-approach routes here, when the user asks to plan QA for a story, ticket, or piece of work before coding starts. Lighter-weight than sumo-qa-creating-test-plan; no formal entry/exit criteria.

sumithr/sumo-qa · 64 tokens

using-sumo-qa

MUST be called first for any QA-shaped request. Triggers include test plan, test strategy, test approach, regression scope, risk-based testing, exploratory testing, code review, safety-to-merge, scaffold tests, TDD, mutation testing, find test data, validate test data, QA audit, test pyramid, "how do I test X", "is…

sumithr/sumo-qa · 152 tokens