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/create-testgit 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/create-test)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/create-test"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/create-test.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.00021 | $0.03004 |
| Opus 5 | $0.00010 | $0.01502 |
| Sonnet 5 | $0.00004 | $0.00601 |
| Haiku 4.5 | $0.00002 | $0.00300 |
Grade A, and why
create-test 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.
How it starts
The opening of the file, as written. The whole thing — 516 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Test File
You are tasked with creating a new test file for the mcp-server-langgraph project. This command automates test file generation using established testing patterns and common fixtures.
Project Testing Context
Test Suite: 437+ tests across 5 categories Coverage: 60-65% (target: 80%) Testing Frameworks:
- pytest (with pytest-asyncio, pytest-cov, pytest-xdist)
- Hypothesis (property-based testing)
- unittest.mock (AsyncMock, MagicMock, patch)
Test Categories:
- Unit Tests (350+) - Fast, no external dependencies
- Integration Tests (50+) - Real infrastructure
- Property Tests (27+) - Hypothesis-based edge case discovery
- Contract Tests (20+) - MCP protocol compliance
- Performance Tests (10+) - Regression tracking
Your Task
Step 1: Gather Information
Ask the user using the AskUserQuestion tool:
Question 1: What module/file do you want to test?
- Header: "Module"
- Provide text input
- Example: "src/mcp_server_langgraph/tools/calculator_tools.py"
- Or: "mcp_server_langgraph.auth.middleware.AuthMiddleware"
Question 2: What type of test?
- Header: "Test Type"
- Options:
- Unit Test: Fast, mocked dependencies
- Integration Test: Real infrastructure (Redis, OpenFGA, etc.)
- Property Test: Hypothesis-based testing
- Contract Test: Protocol/schema validation
Question 3: Does the module use async functions?
- Header: "Async?"
- Options:
- Yes: Uses async/await (most components)
- No: Synchronous only
Step 2: Analyze Module
-
Read the module file to understand:
- Class names and methods
- Function names and signatures
- External dependencies
- Async vs sync patterns
-
Determine what needs testing:
- Public methods/functions
- Edge cases (errors, empty inputs, max values)
- Dependency interactions
Step 3: Generate Test File
File Location:
- Unit tests:
tests/unit/<category>/test_<module_name>.py- Categories:
auth/,core/,llm/,mcp/,observability/,tools/, etc. - Example:
tests/unit/auth/test_auth_middleware.py
- Categories:
- Integration tests:
tests/integration/test_<module_name>.py - Property tests:
tests/property/test_<module_name>.py - Contract tests:
tests/contract/test_<module_name>.py
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.
- 3d ago First seen · 516 lines · 21 tokens per session scan A b2011b36c15d
create-test is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 10d ago), licensed MIT. It adds 21 tokens to every session and 3,004 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
hal-voice-toggle
Toggle HAL 9000 voice clips on or off.
deps-age
Analyze dependency freshness and maintenance activity.
audit-code
When /audit-code [target] is invoked, immediately execute the following steps to analyze code quality, security, and adherence to project standards.
plan-delegate
Execution: work a roadmap as supervisor, brief an implementation agent per item, verify its work independently, then record and commit it.
designer
UI/UX design with Memory coordination for consistent experiences.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.