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.
npx agentmods add commands/esbmc/agent-marketplace/verifygit clone --depth 1 https://github.com/esbmc/agent-marketplaceWrote 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/esbmc/agent-marketplace/verify)<a href="https://agentmods.dev/commands/esbmc/agent-marketplace/verify"><img src="https://agentmods.dev/badge/commands/esbmc/agent-marketplace/verify.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00777 |
| Opus 5 | $0.00008 | $0.00388 |
| Sonnet 5 | $0.00003 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00078 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ESBMC Verification Command
Verify the specified source file using ESBMC bounded model checker.
Instructions
-
Check that ESBMC is installed by running
which esbmc. If not found, stop and tell the user:- Download pre-built binaries from https://github.com/esbmc/esbmc/releases
- Or build from source: https://github.com/esbmc/esbmc
- Ensure
esbmcis in the PATH:export PATH=$PATH:/path/to/esbmc/bin
-
Determine the file type from the extension:
.c→ C file.cpp,.cc,.cxx→ C++ file.py→ Python file (auto-detected by extension).sol→ Solidity file (use--sol).cu→ CUDA file
-
Solver detection — run
esbmc --list-solversand select the best available solver using this priority order: Boolector → Bitwuzla → Z3. Use the corresponding flag:--boolector,--bitwuzla, or--z3. If none of these solvers are listed as available, stop and tell the user that ESBMC is built without solver support, and direct them to build ESBMC with solver support: https://github.com/esbmc/esbmc -
Loop discovery — run
esbmc <file> --show-loopsto list all loops in the program. Then choose the unwind strategy:- No loops found → no unwind flag needed
- Loops with bounds apparent from the source (e.g.,
for (i = 0; i < N; i++)) → use--unwindset L1:N,...with per-loop bounds derived from the source - Loops with unknown or dynamic bounds → use
--incremental-bmc
-
Build and run the verification command using the detected solver flag, chosen unwind strategy, and any checks from the
checksargument:Base command:
esbmc <file> <solver-flag> <unwind-strategy> --timeout 60sAdditional checks based on
checksargument:memory→ add--memory-leak-checkoverflow→ add--overflow-check --unsigned-overflow-checkconcurrent→ add--deadlock-check --data-races-check --context-bound 2all→ add all of the above
-
Interpret the results:
- VERIFICATION SUCCESSFUL → All checked properties hold within bounds
- VERIFICATION FAILED → Bug found, examine counterexample trace
- UNKNOWN/TIMEOUT → Verification inconclusive
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.
- 5d ago First seen · 74 lines · 15 tokens per session scan A d63db5f3e405
verify is a command published in the GitHub repository esbmc/agent-marketplace (4 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 777 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.