Agent skill

Verify

by mag123c in mag123c/toktrack

Self-healing verification loop (test → clippy → fmt). An agent skill from mag123c/toktrack.

MITAuto-check passed

Install Verify

skills CLI
$ npx skills add mag123c/toktrack --skill verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mag123c/toktrack verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mag123c/toktrack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/verify .claude/skills/verify && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verify
GitHub stars
193
Token cost
~676 tokens
SKILL.md length
299 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Self-healing verification loop (test → clippy → fmt). An agent skill from mag123c/toktrack.

  • SKILL.md covers Flow, Commands, Verification Honesty (MUST —… and Self-Healing, plus 2 more sections
  • Calls cargo

What it does

Verify is an agent skill from mag123c/toktrack. Self-healing verification loop (test → clippy → fmt)

Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Ultra-fast token & cost tracker for LLM Token Usage (e.g. Claude Code). The licence is MIT.

Example prompts

  • “/verify”

What it can do on your machine

Read from SKILL.md and the folder at commit 75a86fa. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verify loads about 676 tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 299 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~15
When it runs · the whole SKILL.md, loaded when a task matches
~676

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mag123c/toktrack at commit 75a86fa, republished under its MIT licence (© mag123c). 299 words, ~676 tokens.

Download SKILL.mdSave it as .claude/skills/verify/SKILL.md (or your agent's skills folder).
name
verify
description
Self-healing verification loop (test → clippy → fmt)

Verify

Flow

cargo test → cargo clippy → cargo fmt --check
    │            │              │
    └── On fail: fix and retry (notify user after 3 same failures)

Commands

bash
cargo test --quiet
cargo clippy --all-targets --all-features -- -D warnings
cargo fmt --all -- --check

Verification Honesty (MUST — PASS gate)

Verification trustworthiness lies not in "what passed" but in "what was actually executed and passed". Enforced before any PASS verdict.

Skip ≠ Pass
  • Tests marked ignored / #[ignore] are unverified → do not count as green.
  • Tests skipped due to environment (missing external service, platform constraints, etc.) are a BLOCKER. If unfixable, escalate to user as "verification incomplete + reason" rather than PASS.
Do not cite unrun tests as verification evidence
  • "Confirmed via test X" is only valid when that test actually ran and passed in this execution.
  • Do not use a merely written test as evidence of "confirmed" (false-green = false reassurance).
Coverage honesty (mock ≠ real)
  • Mock-based unit tests verify only the logic inside the mock boundary. Behaviors invisible to mocks — file I/O, concurrency, simd-json real parsing — are confirmed only by integration verification.
  • If a path is covered only by mocks, report it as "mock coverage only — integration unconfirmed" rather than "verified".
Acceptance/DoD cross-check (carry PLAN gates)
  • Read the PLAN Acceptance/DoD and any [unverified-gate] passed from implement; cross-check whether each item actually ran and passed in this execution.
  • If unrunnable (prod smoke / external service / CI-only environment) → no green-wash. Tag as [unverified-gate: delegated, owner/due/probe] and carry to wrap Plan Reconciliation (../wrap/references/reconciliation.md).
Report format
  • ✅ Actually executed and passed
  • ⛔ Skipped/environment-blocked + reason (unresolved = BLOCKER, not PASS)
  • ⚠️ Mock coverage only, integration unconfirmed
  • ⏳ Delegated to wrap due to unverifiable Acceptance item

Self-Healing

  • Fail → analyze error → fix code → retry
  • Same error 3 times → notify user

Rules

  • Required before commit
  • Order: test → clippy → fmt
  • All must pass to proceed

Next Step

Only when the Verification Honesty gate passes (actual execution passed, no unresolved BLOCKERs) → call /review immediately. Do not ask "should I review?".

If there are unresolved BLOCKERs, do not proceed to /review — report "verification incomplete + reason + required environment actions" to the user.

© mag123c, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/verify of mag123c/toktrack.

Open the folder on GitHubat commit 75a86fa

Compare with similar skills

Verify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify this skillmag123c/toktrack193—~676Automated safety check: PassMIT
Clippysundial-org/awesome-openclaw-skills663—~963Automated safety check: PassNone
Run Clippyr3bl-org/r3bl-open-core485—~1.8kAutomated safety check: PassApache-2.0
Convex Self Healopenclaw/clawhub9.5k1 repos~1.4kAutomated safety check: PassMIT
Heal PRrazorpay/blade656—~414Automated safety check: PassMIT
Self Healingpskoett/pskoett-ai-skills311—~5.3kAutomated safety check: NotesNone

Similar skills

  • Clippy

    sundial-org/awesome-openclaw-skills

    Microsoft 365 / Outlook CLI for calendar and email. An agent skill from sundial-org/awesome-openclaw-skills.

    663 GitHub stars~963 tokensUpdated 7 mo ago
    Documents & OfficeAuto-check passed
  • Run Clippy

    r3bl-org/r3bl-open-core

    Run clippy linting, enforce comment punctuation rules, format code with cargo fmt, and verify module organization patterns.

    485 GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Convex Self Heal

    openclaw/clawhub

    Production error → triaged, root-caused, repaired, and certified (tsc + rehearsal + reproduce-then-gone) fix PR for a human to merge — then confirm the error stops recurring.

    9.5k GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Heal PR

    razorpay/blade

    Heal a Blade PR by fixing CI failures, missing changesets, and sanity issues.

    656 GitHub stars~414 tokensUpdated today
    Testing & QAAuto-check passed
  • Self Healing

    pskoett/pskoett-ai-skills

    Active runtime recovery for coding agents: when something breaks mid-task, diagnose the root cause, write a fix, VERIFY by re-running the broken thing, then file a HEAL- entry to .learnings/HEALS.md…

    311 GitHub stars~5.3k tokensUpdated 3 days ago
    DevelopmentAuto-check: notes
  • Rust Clippy Triage

    rocky-data/rocky

    Playbook for when cargo clippy -- -D warnings fires in the Rocky engine.

    304 GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

More from mag123c/toktrack

  • Clarify

    mag123c/toktrack

    Adaptive requirements clarification with auto-depth routing.

    193 GitHub stars~1.3k tokensUpdated 7 days ago
    Auto-check passed
  • Implement

    mag123c/toktrack

    TDD implementation (RED→GREEN→REFACTOR) → verify → review. An agent skill from mag123c/toktrack.

    193 GitHub stars~353 tokensUpdated 7 days ago
    Auto-check passed
  • Review

    mag123c/toktrack

    Multi-agent code review for Rust CLI/TUI. An agent skill from mag123c/toktrack.

    193 GitHub stars~1.2k tokensUpdated 7 days ago
    Auto-check passed
  • Next

    mag123c/toktrack

    Session start - check progress, suggest next task. An agent skill from mag123c/toktrack.

    193 GitHub stars~330 tokensUpdated 7 days ago
    Auto-check passed
  • Wrap

    mag123c/toktrack

    Session end - document updates, commit

    193 GitHub stars~407 tokensUpdated 7 days ago
    Auto-check passed

Questions about Verify

What does Verify do?

Self-healing verification loop (test → clippy → fmt). An agent skill from mag123c/toktrack. Verify is an agent skill from mag123c/toktrack.

How do I install Verify in Claude Code?

Run `npx skills add mag123c/toktrack --skill verify -a claude-code`. Or copy the skill folder (.claude/skills/verify in mag123c/toktrack) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.

How do I install Verify in Codex?

Run `npx skills add mag123c/toktrack --skill verify -a codex`. Or copy the skill folder (.claude/skills/verify in mag123c/toktrack) into .agents/skills/verify in your project. Codex loads it when a task matches its description.

Can I use Verify in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mag123c/toktrack --skill verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify, .gemini/skills/verify, .github/skills/verify and .opencode/skills/verify in your project.

What does Verify need to run?

Going by SKILL.md and its folder, Verify needs the command-line tools its instructions call (cargo).

Does Verify access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Verify safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Verify use?

Verify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify use?

About 676 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verify?

Skills that share tags, products or a category with Verify: Clippy (sundial-org/awesome-openclaw-skills, 663 stars), Run Clippy (r3bl-org/r3bl-open-core, 485 stars), Convex Self Heal (openclaw/clawhub, 9.5k stars) and Heal PR (razorpay/blade, 656 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify?

mag123c (a GitHub user) maintains it in mag123c/toktrack, which has 193 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 1, 2026.

Source: mag123c/toktrack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.