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-failure-analysisgit 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-failure-analysis)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/test-failure-analysis"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/test-failure-analysis.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.00010 | $0.03813 |
| Opus 5 | $0.00005 | $0.01906 |
| Sonnet 5 | $0.00002 | $0.00763 |
| Haiku 4.5 | $0.00001 | $0.00381 |
Grade A, and why
test-failure-analysis 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 — 680 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Failure Analysis
Usage: /test-failure-analysis or /test-failure-analysis --deep
Purpose: Comprehensive analysis of test failures with root cause identification
🔬 What This Command Does
Performs deep analysis of test failures to identify root causes and suggest fixes:
- Runs tests and captures all failures
- Groups failures by pattern/category
- Analyzes stack traces and error messages
- Identifies common root causes
- Suggests fixes with priority
- Generates actionable report
📊 Analysis Workflow
Step 1: Run Tests and Capture Failures
Execute test suite with detailed output:
# Run all tests, don't stop on first failure
uv run --frozen pytest tests/ -v --tb=short --maxfail=100 2>&1 | tee /tmp/test_output.txt
# Alternative: Only run previously failed tests
uv run --frozen pytest --lf -v --tb=long 2>&1 | tee /tmp/test_failures.txt
# Count failures
FAILURES=$(grep -c "FAILED" /tmp/test_output.txt)
ERRORS=$(grep -c "ERROR" /tmp/test_output.txt)
PASSED=$(grep -c "PASSED" /tmp/test_output.txt)
echo "Results: $PASSED passed, $FAILURES failed, $ERRORS errors"
Step 2: Extract Failure Information
Parse test output to extract structured data:
# Extract failed test names
grep "FAILED" /tmp/test_output.txt | \
sed 's/FAILED //' | \
sed 's/ - .*//' > /tmp/failed_tests.txt
# Extract error types
grep -A 5 "FAILED\|ERROR" /tmp/test_output.txt | \
grep -E "Error|Exception|assert" > /tmp/error_types.txt
# Extract file locations
grep "FAILED" /tmp/test_output.txt | \
sed 's/::.*//' | \
sort | uniq -c | \
sort -rn > /tmp/failing_files.txt
Step 3: Categorize Failures
Group failures by error pattern:
Categories:
Assertion Failures (Logic Errors):
AssertionError: assert X == Y
AssertionError: assert result is not None
Import/Module Errors:
ImportError: cannot import name
ModuleNotFoundError: No module named
Async/Event Loop Errors:
RuntimeError: Event loop is closed
asyncio.TimeoutError
RuntimeError: This event loop is already running
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 · 680 lines · 10 tokens per session scan A 102bbdb5c097
test-failure-analysis is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 11d ago), licensed MIT. It adds 10 tokens to every session and 3,813 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.
OPSX: Bulk Archive
Archive multiple completed changes at once.
designer
UI/UX design with Memory coordination for consistent experiences.
reviewer
Code review using batch file analysis for comprehensive reviews.
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.