test-and-validate

A read-only verification procedure for strike-cli changes, covering formatting, generated TUI files, web checks, building, static analysis, and tests. It chooses a verification level based on whether the change affects documentation, Go code, the web interface, or trust boundaries.

In plain words
What is it for?
Use it before claiming work is complete to run the relevant formatting, generation, build, vet, web, unit-test, and race-test checks for the changed areas.
Why use it?
It provides a project-defined set of checks instead of relying on an incomplete local test run. It reports failures and does not modify the code to hide them.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/jonathanung/strike/test-and-validate
Any agent
npx skills add jonathanung/strike --skill test-and-validate
Clone the repo
git clone --depth 1 https://github.com/jonathanung/strike

Made for: Claude Code, Codex.

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,224 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00052 $0.01224
Opus 5 $0.00026 $0.00612
Sonnet 5 $0.00010 $0.00245
Haiku 4.5 $0.00005 $0.00122

Measured 3d ago against content hash 402406dc8757, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-and-validate 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 3d 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.

.claude/skills/test-and-validate/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test and validate (strike-cli)

Read-only verification skill. Observe and report — do not fix failures here (use built-in /verify or implement fixes under issue-handler when owning a branch).

Single source of truth for gates: root AGENTS.mdVerification tiers. This skill runs those tiers; do not invent softer or harder local suites.

CI mirror (order matters)

Match .github/workflows/ci.yml:

  1. gofmt -l . must be empty
  2. go generate ./internal/frontend/tui/app (TUI flatten; required before build/test if _src changed or generate is stale)
  3. make web-check when web/ is touched or web/package.json exists and UI may be affected
  4. go build ./... or make build
  5. make vet
  6. go test ./... — CI uses go test -race ./... on every PR

Local convenience: make test && make vet && make build after gofmt (+ generate/web when needed).

Risk tiers (pick one per change)

Tier When Local gate
A Docs, skills, comments, markdown-only, no Go/web test -z "$(gofmt -l .)" (skip if no .go touched); no full suite required
B Normal Go/web/TUI code (default) gofmt → generate if TUI _srcmake web-check if web/make test && make vet && make build
C Trust boundary: harness/tool, permission, auth, session, engine concurrency/turn loop, protocol wire, sandbox/workspace Tier B + go test -race ./... -count=1 + focused package tests first

CI still runs race on every PR. Do not pay full local race on Tier A/B unless reproducing a CI failure.

Optional: make cover / make cover-check (soft in CI). Offline product smoke: load skill smoke when user-visible startup/input/session/auth paths change.

Commands

Check Command
Format test -z "$(gofmt -l .)"
TUI generate go generate ./internal/frontend/tui/app
Web make web-check
Unit suite make test or go test ./...
Fresh run go test ./... -count=1
Race go test -race ./... -count=1
Coverage make cover / make cover-check
Package focus go test ./harness/tool/ -count=1 -v
Single test go test ./harness/permission/ -run TestEvaluate -count=1 -v
Vet / build make vet / make build
Offline boot make run-echo

Read the full file on GitHub · 100 lines

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. 3d ago First seen · 100 lines · 52 tokens per session scan A 402406dc8757

Subscribe to this mod's changes

test-and-validate is a skill published in the GitHub repository jonathanung/strike (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,224 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

dsh-web-pre-push-checks

Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.

zhu1090093659/dsh-web · 45 tokens

babysit

Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…

kirodotdev/KiroCrew · 137 tokens

azsdk-common-pipeline-analysis

Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…

Azure/azure-sdk-for-net · 192 tokens

harness-setup

HAR: Project init, tool setup, agent config, memory setup, skill mirror sync. Trigger: setup, init, new project, CI/Codex setup, harness-mem, mirror. Do NOT load for: implementation, review, release, planning.

Chachamaru127/claude-code-harness · 57 tokens

managing-github-actions-secrets

Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.

PostHog/posthog-foss · 67 tokens