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-summarygit 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-summary)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/test-summary"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/test-summary.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.03053 |
| Opus 5 | $0.00008 | $0.01527 |
| Sonnet 5 | $0.00003 | $0.00611 |
| Haiku 4.5 | $0.00002 | $0.00305 |
Grade A, and why
test-summary 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 — 545 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Comprehensive Test Summary
Usage: /test-summary or /test-summary <scope>
Scopes:
all- Run all tests and generate complete summary (default)unit- Unit tests onlyintegration- Integration tests onlyquality- Property + contract + regression testsfailed- Analyze failed tests only
🧪 Test Summary Generation
Step 1: Determine Test Scope
Based on $ARGUMENTS, determine which tests to run:
All Tests (default):
pytest -v --tb=short --cov=src --cov-report=term-missing
Unit Tests:
pytest -m unit -v --tb=short --cov=src --cov-report=term-missing
Integration Tests:
pytest -m integration -v --tb=short
Quality Tests:
pytest -m "property or contract or regression" -v --tb=short
Step 2: Run Tests and Collect Results
Execute tests and capture all output:
# Run tests with JSON output
pytest -v --tb=short --json-report --json-report-file=/tmp/test_results.json
# Also capture human-readable output
pytest -v --tb=short 2>&1 | tee /tmp/test_output.txt
Capture:
- Total tests discovered
- Tests passed/failed/skipped
- Test execution time
- Coverage percentage
- Failed test details (if any)
Step 3: Analyze Test Results
Parse test results from JSON and text output:
Summary Statistics:
{
"total": <total tests>,
"passed": <passed count>,
"failed": <failed count>,
"skipped": <skipped count>,
"errors": <error count>,
"pass_rate": <passed / total * 100>,
"duration": <total seconds>,
"coverage": <coverage percentage>
}
Failed Tests (if any):
- Test name and file location
- Failure reason (assertion, exception)
- Stack trace (abbreviated)
- Related code (file:line)
Skipped Tests:
- Test name
- Skip reason
- Category (infrastructure, experimental, etc.)
Step 4: Coverage Analysis
Analyze code coverage:
# Generate detailed coverage report
pytest --cov=src --cov-report=html --cov-report=term-missing
# Parse coverage summary
coverage report | grep "TOTAL"
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 · 545 lines · 0 tokens per session scan A ed4009fb3a02
test-summary is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 11d ago), licensed MIT. It adds 15 tokens to every session and 3,053 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.
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.
bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.
docker-logs
Muestra los logs recientes de un servicio Docker. El usuario puede especificar qué servicio.