A project verification workflow that runs the checks defined for a code repository, such as formatting, linting, type checking, tests, and architecture rules. Linting finds code problems, while type checking catches incorrect use of data types.

It helps verify changes before they are delivered by running the project's configured commands and reporting each result.

It gives one consistent way to check whether a project still follows its rules and whether its code and tests pass.

verify — Skill for Claude Code and Codex by virgoC0der

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 virgoC0der/awesome-claude-code --skill verify

Clone the repo

git clone --depth 1 https://github.com/virgoC0der/awesome-claude-code

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/virgoc0der/awesome-claude-code/verify/github.svg)](https://agentmods.dev/skills/virgoc0der/awesome-claude-code/verify)

Your own site

<a href="https://agentmods.dev/skills/virgoc0der/awesome-claude-code/verify"><img src="https://agentmods.dev/badge/skills/virgoc0der/awesome-claude-code/verify/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/virgoc0der/awesome-claude-code/verify"><img src="https://agentmods.dev/badge/skills/virgoc0der/awesome-claude-code/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 562 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.

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.00029	$0.00562
Opus 5.5	$0.00012	$0.00225
Sonnet 5.5	$0.00006	$0.00112
Haiku 4.5	$0.00003	$0.00056

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

Security

Grade A, and why

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

skills/verify/SKILL.md · 53 lines

How it starts

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

Run the project's verification suite, using the commands declared in .harness/project.md. This skill is project-agnostic — it does not assume any specific language or tooling.

Step 1: Load the project config

ls .harness/project.md 2>/dev/null

If the file exists, read it and use the Commands section verbatim.

If it does not exist:

Detect the project type from manifest files (pyproject.toml, package.json, go.mod, Cargo.toml, pom.xml, etc.).
Fall back to conventional defaults (e.g. pnpm test, go test ./..., cargo test, poetry run pytest).
Tell the user that .harness/project.md is missing and recommend creating one (the harness skill can bootstrap it).

Step 2: Run each check

Execute, in this order, and report each:

#	Check	Command (from project config)
1	Format	`format_check`
2	Imports / lint	`lint`
3	Type check	`typecheck` (skip if not defined)
4	Tests	`test`
5	Architecture compliance	rules from project config (see below)

For the architecture check:

If Architectural Rules.layer_order is declared, get the changed files (git diff --name-only) and confirm none import from a higher layer to a lower one. Use Grep over each changed file's imports.
If Architectural Rules.placement_rules is declared, confirm new files satisfy each rule.
If no rules are declared, run the universal check: no new circular imports.

Step 3: Report

Output a single summary table:

Check	Status	Details
Format	PASS / FAIL	<command output excerpt or "ok">
Lint	PASS / FAIL	…
Typecheck	PASS / FAIL / SKIP	…
Tests	PASS / FAIL / SKIP	<X passed, Y failed, Z skipped>
Architecture	PASS / FAIL / N/A	<rule violated, if any>

For any failure, list the specific files / lines and the suggested fix.

Treat SKIP as legitimate when a category isn't configured (e.g. no typecheck command declared). Don't claim PASS when something was skipped — be explicit.

Read the full file on GitHub · 53 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 · 53 lines · 29 tokens per session scan A 5da11dd70983

Subscribe to this mod's changes

verify is a skill published in the GitHub repository virgoC0der/awesome-claude-code (1 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 562 once invoked, about $0.0001 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-09-12.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

verify