Borrowing it
Nothing to install: this file belongs to vishnu2kmohan/mcp-server-langgraph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vishnu2kmohan/mcp-server-langgraph/main/.claude/commands/type-safety-status.mdgit 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/type-safety-status)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/type-safety-status"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/type-safety-status.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.1 | $0.00020 | $0.03584 |
| Opus 5 | $0.00010 | $0.01792 |
| Sonnet 5 | $0.00004 | $0.00717 |
| Haiku 4.5 | $0.00002 | $0.00358 |
Grade A, and why
type-safety-status 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 8d 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 — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Type Safety Status Tracker
You are tasked with tracking the mypy strict type checking rollout progress for the mcp-server-langgraph project. This command helps manage the gradual migration to full type safety.
Project Type Safety Context
Current Status: 3/11 core modules with strict mypy Target: 11/11 modules with strict type checking Strategy: Gradual rollout, module by module Tool: mypy with strict mode
Strict Mode Benefits:
- Catch type errors before runtime
- Better IDE autocomplete
- Self-documenting code
- Easier refactoring
Your Task
Step 1: Analyze Current mypy Configuration
-
Read mypy configuration:
# Check mypy config cat pyproject.toml | grep -A 20 "\[tool.mypy\]" -
Identify strict modules: Look for
[[tool.mypy.overrides]]sections withstrict = true -
Count total modules:
find src/mcp_server_langgraph -name "*.py" -type f | wc -l
Step 2: Run mypy Analysis
-
Run mypy on all code:
uv run --frozen mypy src/mcp_server_langgraph --show-error-codes --pretty -
Parse mypy output:
- Count total errors
- Group by error code
- Group by file
- Identify patterns
-
Run mypy with strict on non-strict modules:
uv run --frozen mypy src/mcp_server_langgraph/<module>.py --strict --show-error-codes
Step 3: Generate Type Safety Dashboard
Dashboard Format:
╔══════════════════════════════════════════════════════════════════╗
║ TYPE SAFETY STATUS ║
║ mcp-server-langgraph ║
╠══════════════════════════════════════════════════════════════════╣
║ Strict Modules: 3/11 [███░░░░░░░░░░░░░░░░░░░] 27% ║
║ Target: 11/11 [████████████████████████] 100% ║
║ Progress: +8 [⚠️ 8 modules remaining] ║
║ mypy Errors: 47 [🔴 Need fixing before strict] ║
║ Error Types: 9 [Most common: type-arg, no-untyped] ║
╠══════════════════════════════════════════════════════════════════╣
║ Trend: 📈 [+1 module/sprint] ║
║ ETA to Full Strict: 8wk [At current pace] ║
╚══════════════════════════════════════════════════════════════════╝
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.
- 8d ago First seen · 399 lines · 20 tokens per session scan A 6831fd16e3df
type-safety-status is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 3,584 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
python-dev
Start Python development workflow with architecture, implementation, review, and testing phases.
setup:python
Set up a new Python project with quality tools and Claude framework integration.
ccc-python-review
Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.
notebook-review
Comprehensive review of Jupyter notebooks and Python scripts.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.