OPSX: Verify

OPSX: Verify is a command for Claude Code from Artexis10/exomem. It costs 13 tokens per session (1,590 once invoked), scanned A, original, AGPL-3.0.

A verification command for checking that an implementation matches the files and records describing a requested change before it is archived.

In plain words
What is it for?
Use it to review completed implementation work against its change artifacts before archiving it.
Why use it?
It helps catch differences between the completed code and the change description before the work is closed.

Command for Claude Code

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/artexis10/exomem/verify
Clone the repo
git clone --depth 1 https://github.com/Artexis10/exomem

Made for: Claude Code.

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.

agentmods badge for OPSX: Verify

README.md
[![agentmods](https://agentmods.dev/badge/commands/artexis10/exomem/verify.svg)](https://agentmods.dev/commands/artexis10/exomem/verify)
Your own site
<a href="https://agentmods.dev/commands/artexis10/exomem/verify"><img src="https://agentmods.dev/badge/commands/artexis10/exomem/verify.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,590 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00013 $0.01590
Opus 5 $0.00006 $0.00795
Sonnet 5 $0.00003 $0.00318
Haiku 4.5 $0.00001 $0.00159

Measured 3d ago against content hash 1977f0a348c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

OPSX: 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 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.

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.

.claude/commands/opsx/verify.md · 169 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 3d ago First seen · 169 lines · 13 tokens per session scan A 1977f0a348c3

Subscribe to this mod's changes

OPSX: Verify is a command published in the GitHub repository Artexis10/exomem (10 stars, last pushed today), licensed AGPL-3.0. It adds 13 tokens to every session and 1,590 once invoked, about $0.0001 per session on Opus 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-08-31.