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.
git clone --depth 1 https://github.com/ruslan-korneev/claude-pluginsWrote 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/ruslan-korneev/claude-plugins/typecheck)<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/typecheck"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/typecheck/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/typecheck"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/typecheck.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.00551 |
| Opus 5.5 | $0.00006 | $0.00220 |
| Sonnet 5.5 | $0.00003 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
typecheck 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 1mo 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.
What it actually says
Command /types:check
Run type checking and show errors with explanations.
Instructions
Step 1: Determine the tool
Check for configuration:
# mypy
test -f pyproject.toml && grep -q "tool.mypy" pyproject.toml && echo "mypy configured"
# pyright
test -f pyrightconfig.json && echo "pyright configured"
Step 2: Run the check
# mypy
mypy {{ path | default: "src/" }} --show-error-codes
# pyright
pyright {{ path | default: "src/" }}
Step 3: Group errors
Error categories:
- Missing return type — no return type annotation
- Incompatible types — incompatible types in assignment/call
- Missing type annotation — no annotation for variable
- Optional handling — working with Optional without None check
- Generics — errors with generic types
Step 4: Show solutions
For each error show:
- What the error means
- How to fix it WITHOUT
type: ignore
NEVER SUGGEST
# NEVER:
result = some_function() # type: ignore
value: Any = something # Avoid Any
cast(SomeType, value) # Only if there's no other way
Response Format
## Type Checking Results
### Tool: mypy
### Path: {{ path }}
### Errors found: X
#### Missing return type (N)
- `src/services/user.py:45` — `def process()` → add `-> None` or specific type
#### Incompatible types (N)
- `src/repositories/order.py:23` — `str` vs `int` → convert types explicitly
#### Optional handling (N)
- `src/api/routes.py:67` — possible `None` → add check `if value is not None`
### How to Fix
1. Add return type annotations to functions without them
2. Use `if x is not None` instead of `cast` or `type: ignore`
3. Replace `Any` with specific types or `TypeVar`
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.
- 1mo ago First seen · 93 lines · 16 tokens per session scan A 73fdeb44fb4e
typecheck is a command published in the GitHub repository ruslan-korneev/claude-plugins (5 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 551 once invoked, about $0.0001 per session on Opus 5.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
async-check
Vérification Patterns Async Python.
type-coverage
Vérification Couverture des Types Python.
python-dev
Start Python development workflow with architecture, implementation, review, and testing phases.
py-structure
Analyze and recommend project structure improvements. Checks file sizes, layer organization, module splitting, and hexagonal architecture compliance.
setup
Interactive setup for Python LSP development environment.
debug
A debugging command that sends an error, log, or screenshot to a debugger agent for analysis. The debugger reports confirmed facts separately from possible explanations and does not modify files.