verify

A command that runs only the verification checks linked to the files changed in the current task. It uses the project's verification matrix, which maps types of files to the tests or checks they need.

In plain words
What is it for?
Use it after editing files to find the right checks, run them, stop at the first failure, and record the result.
Why use it?
It avoids spending time on an unnecessary full test run while still checking the parts affected by the change.

Command

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.

agentmods
npx agentmods add commands/kouroshez/coding-os/verify
Clone the repo
git clone --depth 1 https://github.com/kouroshez/coding-os
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 387 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00387
Opus 5 $0.00000 $0.00193
Sonnet 5 $0.00000 $0.00077
Haiku 4.5 $0.00000 $0.00039

Measured yesterday against content hash 16d9a2a0dc8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

src/core/commands/verify.md · 35 lines

What it actually says

Run the matrix-targeted verification commands for files that have changed in the current task.

Per ../rules/test-discipline.md: never pytest tests/ -q mid-task (6 min full sweep). Only run the matrix command(s) tied to changed files.

Steps:

  1. Determine the change scope:
    • If $ARGUMENTS is provided (file paths), use them.
    • Otherwise run git diff --name-only + git status --porcelain to gather changed files.
  2. Map each changed path to its matrix row (from AGENTS.md §Verification Matrix). Surface conflicts: if a file matches no row, ask the user before guessing.
  3. Build the deduped list of commands to run.
  4. State the plan: "I will run: ". Show it before executing — gives the user a chance to redirect.
  5. Run each command. Stream output. Stop at first FAIL with the failing line surfaced.
  6. On success: append a short work-log note via cos_work_log_append(task_id=<current>, summary=<one line>).
  7. On failure: do NOT mark the task complete. Suggest: keep in testing, fix the failure, re-run.

When a full sweep IS allowed (state it out loud first — per test-discipline.md):

  • Pre-merge final gate.
  • Cross-cutting refactor touching ≥3 matrix rows.
  • User explicitly asked "run all tests".

Output format:

## Verification — {N} command(s)

### Plan
- {file pattern} → `{command}`

### Results
- ✅ `{command}` — {duration}
- ❌ `{command}` — {failure summary}, see {line}

### Next step
{recommendation}
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. yesterday First seen · 35 lines · 0 tokens per session scan A 16d9a2a0dc8d

Subscribe to this mod's changes

verify is a command published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 387 tokens. 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-31.