A work-checking procedure that runs the validation tests or checks linked from an issue and reports each result.

Use it before closing an issue or pull request, or when someone asks whether an issue is complete. It maps validation IDs to commands or CI steps and runs them.

It helps confirm that an issue is really finished instead of trusting its claim alone. It also shows which specific checks passed or failed.

How tikoci/rosetta configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tikoci/rosetta. 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/tikoci/rosetta/main/.github/skills/verify-task/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/tikoci/rosetta

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tikoci/rosetta/verify-task/github.svg)](https://agentmods.dev/skills/tikoci/rosetta/verify-task)

Your own site

<a href="https://agentmods.dev/skills/tikoci/rosetta/verify-task"><img src="https://agentmods.dev/badge/skills/tikoci/rosetta/verify-task/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tikoci/rosetta/verify-task"><img src="https://agentmods.dev/badge/skills/tikoci/rosetta/verify-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,423 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00047	$0.01423
Opus 5.5	$0.00019	$0.00569
Sonnet 5.5	$0.00009	$0.00285
Haiku 4.5	$0.00005	$0.00142

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

Security

Grade A, and why

verify-task 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.

.github/skills/verify-task/SKILL.md · 98 lines

How it starts

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

Verify Task

Closes the loop between a work item's claimed acceptance and what's actually proven. Reads the V-* rows cited in the issue's ## Validation section (per the work-item template), looks each up in VALIDATION.md, runs the proof, reports green/red.

When to use

A PR is about to claim Closes #N and you want to confirm the cited validation rows are actually green.
A user asks "is this issue really finished?"

When NOT to use

For an issue that cites no V-* rows (pure-doc work). There's nothing to run.
As a substitute for code review.

Procedure

Resolve the work item. An issue number → gh issue view <n> and pull the V-* IDs from its ## Validation section — falling back to scanning acceptance bullets for older issues that predate the template (also check any archived tasks/done/T-*.md file the issue names as its full spec). T-0037 → read tasks/T-0037-npm-prerelease-dist-tag-channel.md frontmatter directly (the one still-in-flight file-based task).
Look up each V-* in VALIDATION.md. Pull the Proven by, Status, and Tracked by columns. This tells you whether the invariant is already enforced, non-blocking, CI-only, or still a declared gap.

Run the proof.

Run make verify — it covers V-typecheck, V-lint, V-unit, V-tool-registry, and V-retrieval-floor in one command (requires a populated DB). It runs bun test src/mcp-contract.test.ts without ROSETTA_REAL_DB_TESTS=1, so the real-DB blocks behind V-tool-shapes and V-tool-budget are skipped — run those separately with ROSETTA_REAL_DB_TESTS=1 bun test src/mcp-contract.test.ts against a populated DB. For CI-only invariants (V-db-min-content, V-bunx-*) there is no local equivalent; those are only proven by a release run.

For more targeted checks, map common V-* IDs to commands:

V-* ID	Command
V-typecheck	`bun run typecheck`
V-lint	`bun run lint`
V-unit	`bun test`
V-tool-registry	`bun test src/mcp-contract.test.ts` (Block A, always runs)
V-tool-shapes	`ROSETTA_REAL_DB_TESTS=1 bun test src/mcp-contract.test.ts` (Block C, needs populated DB)
V-tool-budget	`ROSETTA_REAL_DB_TESTS=1 bun test src/mcp-contract.test.ts` (Block B, needs populated DB)
V-retrieval-floor	`bun run src/eval/retrieval.ts`
V-retrieval-self	`bun run src/eval/self-supervised.ts`
V-canonicalize	`bun test src/canonicalize.test.ts src/canonicalize.fuzz.test.ts`
V-classifier	`bun test src/classify.test.ts`
V-schema-roundtrip	`bun test src/schema-roundtrip.test.ts`
V-extract-videos	`bun test src/extract-videos.test.ts`
V-http-handshake	`bun test src/mcp-http.test.ts`
V-stdio-handshake	`bun test src/mcp-stdio-client.test.ts`
V-tui-mcp-parity	`bun test src/browse-parity.test.ts`
V-cli-flag-uniformity	`bun test src/cli-help.test.ts`
V-db-wipe-guard	`bun test src/query.test.ts`
V-release-structure	`bun test src/release.test.ts`

Read the full file on GitHub · 98 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.

1mo ago First seen · 98 lines · 47 tokens per session scan A 59f2a672c569

Subscribe to this mod's changes

verify-task is a skill published in the GitHub repository tikoci/rosetta (51 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,423 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.

Claude Code Planning Testing ai bun copilot mcp mcp-server

rosetta: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Verify Task

When to use

When NOT to use

Procedure

What this file has done since we first saw it

Other skills, from other repositories

coding-agents-hooks-authoring

testgen-flow

api-aqa-flow

ui-aqa-flow

qa-knowledge

coding-flow