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.
git clone --depth 1 https://github.com/kouroshez/coding-osWrote 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.
[](https://agentmods.dev/commands/kouroshez/coding-os/verify)<a href="https://agentmods.dev/commands/kouroshez/coding-os/verify"><img src="https://agentmods.dev/badge/commands/kouroshez/coding-os/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.
<a href="https://agentmods.dev/commands/kouroshez/coding-os/verify"><img src="https://agentmods.dev/badge/commands/kouroshez/coding-os/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00387 |
| Opus 5.5 | $0.00000 | $0.00155 |
| Sonnet 5.5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00039 |
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.
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:
- Determine the change scope:
- If
$ARGUMENTSis provided (file paths), use them. - Otherwise run
git diff --name-only+git status --porcelainto gather changed files.
- If
- 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.
- Build the deduped list of commands to run.
- State the plan: "I will run: ". Show it before executing — gives the user a chance to redirect.
- Run each command. Stream output. Stop at first FAIL with the failing line surfaced.
- On success: append a short work-log note via
cos_work_log_append(task_id=<current>, summary=<one line>). - On failure: do NOT mark the task
complete. Suggest: keep intesting, 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}
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 · 35 lines · 0 tokens per session scan A 16d9a2a0dc8d
verify is a command published in the GitHub repository kouroshez/coding-os (7 stars, last pushed 2d ago), 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.
Other commands, from other repositories
slm-loop
Run a task as a bounded, gate-verified loop backed by SuperLocalMemory — iterate until an independent gate passes, never on the agent's own claim.
gsd:eval-review
Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
coverage
Add test coverage to existing code.
develop-staged-tdd
Orchestrate multi-agent staged development with TDD and quality gates.
gsd-review
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.
gsd:add-tests
Generate tests for a completed phase based on UAT criteria and implementation.