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/vishnu2kmohan/mcp-server-langgraph/test-fastgit 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/test-fast)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/test-fast"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/test-fast.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.00009 | $0.02046 |
| Opus 5 | $0.00005 | $0.01023 |
| Sonnet 5 | $0.00002 | $0.00409 |
| Haiku 4.5 | $0.00001 | $0.00205 |
Grade A, and why
test-fast 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 4d 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 — 407 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fast Test Iteration
Usage: /test-fast or /test-fast <mode>
Purpose: Execute tests with optimized speed for rapid development iteration
Modes:
dev- Development mode (recommended)core- Fastest core tests onlyparallel- All tests in parallelunit- Unit tests only (no coverage)
🚀 Why Fast Testing?
Standard test execution with coverage can be slow:
make test: ~45-60 seconds (with coverage)make test-unit: ~30-40 seconds (with coverage)
Fast testing options provide 40-70% speed improvement for rapid iteration:
make test-dev: ~15-20 seconds ⚡make test-fast-core: ~3-5 seconds ⚡⚡make test-fast: ~20-30 seconds ⚡
⚡ Fast Testing Options
Development Mode (RECOMMENDED)
Best for active development - parallel, fast-fail, skip slow tests:
make test-dev
```rust
**Features**:
- ✅ Parallel execution (`pytest -n auto`)
- ✅ Stop on first failure (`-x`)
- ✅ Max 3 failures (`--maxfail=3`)
- ✅ Skip slow tests (`-m "unit and not slow"`)
- ✅ No coverage overhead
- ✅ Short traceback (`--tb=short`)
**Speed**: 40-60% faster than standard tests
**Use case**: Active development, quick feedback loop
**Example output**:
Running tests in development mode (parallel, fast-fail, no coverage)... ✓ Development tests complete
Features: Parallel execution, stop on first failure, skip slow tests
---
### Fastest Core Tests
Minimal test set for ultra-rapid iteration:
```bash
make test-fast-core
Features:
- ✅ Core unit tests only
- ✅ Parallel execution
- ✅ No slow tests
- ✅ No integration tests
- ✅ Minimal output (
-q)
Speed: Typically < 5 seconds ⚡⚡ Use case: Rapid iteration on critical paths
Example:
⚡ Running core unit tests only (fastest iteration)...
✓ Core tests complete
Use for rapid iteration (typically < 5 seconds)
All Tests (No Coverage)
Run all tests without coverage overhead:
make test-fast
```bash
**Features**:
- ✅ All unit and integration tests
- ✅ Parallel execution
- ✅ No coverage collection
- ✅ Short traceback
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.
- 4d ago First seen · 407 lines · 9 tokens per session scan A 6c608ce22a52
test-fast is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 11d ago), licensed MIT. It adds 9 tokens to every session and 2,046 once invoked, about $0.0000 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
hal-voice-toggle
Toggle HAL 9000 voice clips on or off.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
frappe-test
Run unit and integration tests for Frappe apps with coverage reports.
setup
Command "setup" from jazz-max/ruflo-hub, covering setting up ruv-swarm hooks, quick start, 1. initialize with hooks, 2. test hook functionality and test pre-edit hook.
agent-metrics
Command "agent-metrics" from jazz-max/ruflo-hub, covering agent-metrics, usage, options, examples and all agents metrics.