test-summary

test-summary is a command for Claude Code from vishnu2kmohan/mcp-server-langgraph. It costs 15 tokens per session (3,053 once invoked), scanned A, original, MIT.

A command that runs selected tests and produces a detailed result summary, including passes, failures, skips, execution time, and coverage. Unit tests check small pieces of code; integration tests check how parts work together.

In plain words
What is it for?
Use it to summarise all tests or only unit, integration, quality, or failed tests, with terminal output and optional JSON results.
Why use it?
It collects test output and failure details in one report, making it easier to understand the health of a test run.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/vishnu2kmohan/mcp-server-langgraph/test-summary
Clone the repo
git clone --depth 1 https://github.com/vishnu2kmohan/mcp-server-langgraph

Made for: Claude Code.

Wrote 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.

agentmods badge for test-summary

README.md
[![agentmods](https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/test-summary.svg)](https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/test-summary)
Your own site
<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>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,053 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash ed4009fb3a02, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/commands/test-summary.md · 545 lines

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 only
  • integration - Integration tests only
  • quality - Property + contract + regression tests
  • failed - 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"

Read the full file on GitHub · 545 lines

Changes

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.

  1. 4d ago First seen · 545 lines · 0 tokens per session scan A ed4009fb3a02

Subscribe to this mod's changes

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.