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/coverage-trendgit 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/coverage-trend)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/coverage-trend"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/coverage-trend.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.02891 |
| Opus 5 | $0.00005 | $0.01445 |
| Sonnet 5 | $0.00002 | $0.00578 |
| Haiku 4.5 | $0.00001 | $0.00289 |
Grade A, and why
coverage-trend 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 — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Trend Analysis
Usage: /coverage-trend or /coverage-trend --days 30
Purpose: Track test coverage trends over time and identify patterns
Features 🆕:
- Historical coverage tracking
- Trend visualization
- Module-level breakdown
- Coverage delta analysis
- Regression detection
📊 What This Command Does
Analyzes test coverage evolution over time by:
- Running current coverage measurement
- Reading historical coverage data
- Computing trends and changes
- Identifying coverage gaps
- Generating trend visualization
🚀 Execution Steps
Step 1: Run Current Coverage
Execute coverage measurement:
# Run combined coverage (unit + integration)
make test-coverage-combined
# This generates:
# - htmlcov-combined/index.html (HTML report)
# - coverage.xml (XML report)
# - .coverage (raw data)
Step 2: Extract Coverage Metrics
Parse coverage results:
# Total coverage percentage
CURRENT_COV=$(grep -oP 'Total coverage: \K[0-9.]+' coverage.xml || \
coverage report --format=total 2>/dev/null || \
echo "unknown")
# Module-level coverage
coverage report --format=markdown > /tmp/coverage_by_module.md
# Or parse HTML
grep -A 5 "Total" htmlcov-combined/index.html
Step 3: Load Historical Data
Read stored coverage history:
# Coverage history stored in .coverage-history/
# Format: YYYY-MM-DD,coverage_percentage,modules_covered
# Create if doesn't exist
mkdir -p .coverage-history
# Append current measurement
echo "$(date +%Y-%m-%d),$CURRENT_COV" >> .coverage-history/trend.csv
Step 4: Calculate Trends
Analyze coverage evolution:
# Last 7 days average
tail -7 .coverage-history/trend.csv | awk -F',' '{sum+=$2; count++} END {print sum/count}'
# Last 30 days average
tail -30 .coverage-history/trend.csv | awk -F',' '{sum+=$2; count++} END {print sum/count}'
# Trend direction
# Compare last 7 days vs previous 7 days
Step 5: Generate Visualization
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 · 486 lines · 9 tokens per session scan A ce3b96c08e54
coverage-trend 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,891 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.
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.