agentmods.dev

check-work

check-work is a skill for Claude Code, Codex from codingmydna/grokers. It costs 64 tokens per session (2,860 once invoked), scanned A, a copy of check-work, Apache-2.0.

A self-check procedure that uses another agent to review changes, run builds and tests, and judge whether the work is correct.

In plain words
What is it for?
It is for verifying code changes, checking a particular focus area, and repeating fixes until the verifier passes the work.
Why use it?
It helps catch mistakes or incomplete changes before the work is considered finished.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions AGENTS.md.

not rated 4repo 3mo ago A scan 64 tokens copy · 100% Apache-2.0

Good fit It is for verifying code changes, checking a particular focus area, and repeating fixes until the verifier passes the work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/codingmydna/grokers/check-work
View source ↗ codingmydna/grokers
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.

Any agent
npx skills add codingmydna/grokers --skill check-work
Clone the repo
git clone --depth 1 https://github.com/codingmydna/grokers

Made for: Claude Code, Codex.

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 check-work

README.md
[![agentmods](https://agentmods.dev/badge/skills/codingmydna/grokers/check-work/github.svg)](https://agentmods.dev/skills/codingmydna/grokers/check-work)
Your own site
<a href="https://agentmods.dev/skills/codingmydna/grokers/check-work"><img src="https://agentmods.dev/badge/skills/codingmydna/grokers/check-work/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 check-work

Your own site · 80×15
<a href="https://agentmods.dev/skills/codingmydna/grokers/check-work"><img src="https://agentmods.dev/badge/skills/codingmydna/grokers/check-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,860 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00064 $0.02860
Opus 5.5 $0.00026 $0.01144
Sonnet 5.5 $0.00013 $0.00572
Haiku 4.5 $0.00006 $0.00286

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

Security

Grade A, and why

check-work scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Running the application and exercising it (curl endpoints, invoke CLIs)
Origin

This is a copy

100% identical to check-work — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

crates/codegen/xai-grok-shell/skills/check-work/SKILL.md · 288 lines

How it starts

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

/check-work -- Self-Verification

Verify work by spawning a verifier subagent, checking its verdict, and fixing issues until it passes.

Usage

/check-work [focus area]

The optional focus area tells the verifier to pay special attention to specific aspects of the changes (e.g. "auth logic and JWT handling").

Mode Detection

Determine which mode you are in before proceeding:

  • Same-turn mode: There is a user task alongside this skill (e.g. headless --check). Complete the task fully first, then proceed to Step 1 below.
  • Standalone mode: There is no task — just /check-work (or the alias /check) or the skill was invoked after a previous turn. Proceed directly to Step 1.

Steps

  1. Call the task tool with:

    • description: must start with "[checking my work]" followed by a short label
    • subagent_type: "general-purpose"
    • run_in_background: false
    • prompt: copy the VERIFIER PROMPT section below verbatim. If a focus area was specified by the user, append this to the prompt: 
      ## Additional Focus
<focus area text>
Pay special attention to these areas during verification.

  2. Read the subagent's result. Look for VERDICT: PASS or VERDICT: FAIL.

  3. If PASS: summarize what the verifier confirmed and stop.

  4. If FAIL (or no verdict found): fix the issues the verifier identified, then go back to step 1. Repeat up to 3 times.

VERIFIER PROMPT

You are an expert verifier. Your job is to determine whether the work done in this session correctly and completely addresses the user's requests.

You already have the full conversation context, so you know what the user asked for, what approach was taken, what tools were used, and what outcomes were observed. You also have full access to the same environment and tools the original agent had.

=== SCOPE ===

Determine what to verify:

  • If a focus area was specified (see Additional Focus below), verify that specific area. Use the full session trace for context -- understand what was asked, what was done, and what state the environment is in -- but scope your verdict to the focused area.
  • If no focus area was specified, verify all work done in this session.

Read the full file on GitHub · 288 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. 1mo ago First seen · 288 lines · 64 tokens per session scan A 51a57345db2b

Subscribe to this mod's changes

check-work is a skill published in the GitHub repository codingmydna/grokers (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 2,860 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to check-work, differing in 0 lines, and is treated as a copy.

Code reviewTestingai-agentanthropicbyokclaudecoding-agentgrok
Related

Other skills, from other repositories

receiving-code-review

Handle review feedback on code with care: understand each point, check it against the real code before changing anything, fix what is right, and push back with reasons on what is wrong. Use when review comments arrive.

androoAGI/starnet · 48 tokens

remove-ai-slops

Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.

code-yeongyu/oh-my-openagent · 45 tokens

semgrep-rule-variant-creator

Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.

waybarrios/opencode-power-pack · 50 tokens

fable-judge

Adversarial verification of finished work. Treats any "done" as a set of claims, then re-runs the claimed verifications, diffs what actually changed, detects weakened tests and false completion claims, and delivers an evidence-based verdict (VERIFIED / VERIFIED WITH CAVEATS / REFUTED). Use after any agent or model…

Sahir619/fable-method · 124 tokens

code-guidelines-go

Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…

dimetron/pi-go · 124 tokens

ln-42-dependency-upgrader

Upgrades dependencies in reversible batches with version-specific compatibility and regression checks.

levnikolaevich/claude-code-skills · 22 tokens