Borrowing it
Nothing to install: this file belongs to jonathanung/strike. 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/jonathanung/strike/main/.claude/skills/test-and-validate/SKILL.mdgit clone --depth 1 https://github.com/jonathanung/strikeWrote 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/jonathanung/strike/test-and-validate)<a href="https://agentmods.dev/skills/jonathanung/strike/test-and-validate"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/test-and-validate/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/jonathanung/strike/test-and-validate"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/test-and-validate.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.00052 | $0.01224 |
| Opus 5.5 | $0.00021 | $0.00490 |
| Sonnet 5.5 | $0.00010 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
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 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.
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.md → Verification tiers.
This skill runs those tiers; do not invent softer or harder local suites.
CI mirror (order matters)
Match .github/workflows/ci.yml:
gofmt -l .must be emptygo generate ./internal/frontend/tui/app(TUI flatten; required before build/test if_srcchanged or generate is stale)make web-checkwhenweb/is touched orweb/package.jsonexists and UI may be affectedgo build ./...ormake buildmake vetgo test ./...— CI usesgo 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 _src → make 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 |
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 · 100 lines · 52 tokens per session scan A 402406dc8757
test-and-validate is a skill published in the GitHub repository jonathanung/strike (5 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 1,224 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-31.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
quality-scan
Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.
e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
test-setup
Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…