Borrowing it
Nothing to install: this file belongs to vishnu2kmohan/mcp-server-langgraph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vishnu2kmohan/mcp-server-langgraph/main/.claude/commands/verify-tests.mdgit clone --depth 1 https://github.com/vishnu2kmohan/mcp-server-langgraphWrote 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/vishnu2kmohan/mcp-server-langgraph/verify-tests)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/verify-tests"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/verify-tests/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/vishnu2kmohan/mcp-server-langgraph/verify-tests"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/verify-tests.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.00014 | $0.01546 |
| Opus 5.5 | $0.00006 | $0.00618 |
| Sonnet 5.5 | $0.00003 | $0.00309 |
| Haiku 4.5 | $0.00001 | $0.00155 |
Grade A, and why
verify-tests 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.
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify All Tests Pass
Run comprehensive test verification to ensure all tests pass before committing or merging.
Usage
/verify-tests
```bash
## Test Execution Workflow
### Step 1: Unit Tests (Fast - ~2 minutes)
```bash
make test-unit
```bash
**What it tests**:
- Pure unit tests with mocked dependencies
- No external services required
- Fast execution (< 1s per test ideally)
**Success criteria**: All unit tests PASS
### Step 2: Integration Tests (~5 minutes)
```bash
make test-integration
```bash
**What it tests**:
- Tests with real dependencies (PostgreSQL, Redis, etc.)
- API endpoint tests
- Database query tests
- Authentication flows
**Prerequisites**:
- Infrastructure running: `make setup-infra`
- Services healthy: `docker-compose ps`
**Success criteria**: All integration tests PASS
### Step 3: Property-Based Tests (~2 minutes)
```bash
make test-property
```bash
**What it tests**:
- Edge case discovery using Hypothesis
- Randomized input validation
- Invariant testing
**Success criteria**: All property tests PASS
### Step 4: Contract Tests (~1 minute)
```bash
make test-contract
```bash
**What it tests**:
- MCP protocol compliance
- OpenAPI schema validation
- API contract adherence
**Success criteria**: All contract tests PASS
### Step 5: Security Tests (~1 minute)
```bash
pytest tests/security/ -v
```bash
**What it tests**:
- OWASP Top 10 vulnerabilities
- Authentication/authorization
- Input validation
- SQL injection prevention
- XSS prevention
**Success criteria**: All 34 security tests PASS
### Step 6: Test Coverage Check
```bash
pytest --cov=src --cov-report=term-missing --cov-fail-under=64 tests/
```bash
**Success criteria**:
- Coverage ≥ 64% (CI threshold)
- No critical gaps in coverage
- New code has ≥ 80% coverage
## Comprehensive Test Run
Run all tests in one command:
```bash
make test-all-quality
```bash
**Includes**:
- Unit tests
- Integration tests
- Property tests
- Contract tests
- Security tests
- Regression tests
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 · 304 lines · 14 tokens per session scan A 6a78a69d9303
verify-tests is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 1,546 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-08-31.
Other commands, from other repositories
test-coverage
Analyze and improve test coverage.
verify
Run verification loop to validate implementation.
test-suite
Run comprehensive test suite with coverage analysis.
test-coverage
Analyze test coverage and generate missing tests to reach 80%+ coverage.
write-tests
Generate a focused, production-quality test suite for a source file, detecting the project's existing test runner and conventions. Use when a source file needs a test suite that matches the project's existing conventions.
test-gen
Generate comprehensive tests for a specified file with edge cases and error scenarios.