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.
npx agentmods add skills/codingmydna/grokers/check-worknpx skills add codingmydna/grokers --skill check-workgit clone --depth 1 https://github.com/codingmydna/grokersWhat 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 | $0.00064 | $0.02860 |
| Opus 5 | $0.00032 | $0.01430 |
| Sonnet 5 | $0.00013 | $0.00572 |
| Haiku 4.5 | $0.00006 | $0.00286 |
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 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.
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) 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.
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
-
Call the
tasktool with:description: must start with"[checking my work]"followed by a short labelsubagent_type:"general-purpose"run_in_background:falseprompt: 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.
-
Read the subagent's result. Look for
VERDICT: PASSorVERDICT: FAIL. -
If PASS: summarize what the verifier confirmed and stop.
-
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.
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.
- 3d ago First seen · 288 lines · 64 tokens per session scan A 51a57345db2b
check-work is a skill published in the GitHub repository codingmydna/grokers (4 stars, last pushed 1mo 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. 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.
Other skills, from other repositories
grok-runtime
Internal helper contract for calling the grok-companion runtime from Claude Code or Codex. Reference when invoking the Grok companion script or the groksearch MCP tool.
Review a GitHub PR (via gh)
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the gh CLI or the GitHub MCP server.
Best of N (parallel attempts)
Delegate N parallel subagents on the same task, then pick the best result.
Design doc (write -> review loop)
Draft a design document and iterate writer/reviewer subagents until consensus.
Implement (multi-agent loop)
Orchestrate an implement -> review -> fix loop with subagents until reviewers sign off.
PR babysit (watch & drive to green)
Watch a pull request and delegate fixes until CI is green and reviews are addressed. Requires the GitHub MCP server or gh.