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 skills add MSApps-Mobile/claude-plugins --skill python-lspgit clone --depth 1 https://github.com/MSApps-Mobile/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/skills/msapps-mobile/claude-plugins/python-lsp)<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/python-lsp"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/python-lsp/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/skills/msapps-mobile/claude-plugins/python-lsp"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/python-lsp.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.00121 | $0.01176 |
| Opus 5.5 | $0.00048 | $0.00470 |
| Sonnet 5.5 | $0.00024 | $0.00235 |
| Haiku 4.5 | $0.00012 | $0.00118 |
Grade A, and why
python-lsp 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 today.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
python-lsp — Python code intelligence via Pyright
Part of the LSP plugin series. Wraps Pyright (pyright-langserver)
as a read-only, SOSA Level 1 intelligence source.
Workflow Process
Plan
- Confirm the user's question actually needs semantic info (type diagnostics, references, definitions, hover) vs a plain grep/glob.
- Verify
pyright-langserver --versionworks. If missing, runnpm install -g pyrightorpip install pyright. - Confirm the repo has a recognizable Python root:
pyrightconfig.json,pyproject.toml,setup.py,setup.cfg, or a.gitdirectory.
Act
- Resolve the file path the user is asking about.
- Use LSP via the plugin's
.lsp.jsonwiring:textDocument/publishDiagnostics→ type/import errorstextDocument/definition→ jump to definitiontextDocument/references→ all call sitestextDocument/hover→ inferred type / docstringworkspace/symbol→ fuzzy symbol search
- For cross-file impact (e.g. reviewing a change), iterate
find-referencesover every public symbol in the touched file. - Treat Pyright answers as authoritative over heuristic search. If Pyright returns empty references, say so — don't invent them.
Verify
- Cross-check one reported reference by opening the referenced file. If the symbol isn't really there, the Pyright index may be stale — report that.
- If diagnostics include
reportMissingImportsfor installed packages, the virtual environment isn't configured — checkpyrightconfig.jsonvenvPath/venvsettings before trusting import counts.
Pyright startup notes
- Incremental cache: Pyright writes
.pyright/to the workspace root. Safe to delete to force a full reindex. Subsequent runs are fast. - Virtual environments: Set
venvPath+venvinpyrightconfig.json(orpythonPathfor a specific interpreter) so Pyright resolves installed packages correctly. - Type checking modes:
off→basic→standard→strict. The plugin sendsbasicviasettings.python.analysis(a projectpyrightconfig.jsonoverrides it); upgrade tostandardorstrictfor well-typed codebases where you want exhaustive checking.
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.
- today First seen · 110 lines · 121 tokens per session scan A 0087a04b1126
python-lsp is a skill published in the GitHub repository MSApps-Mobile/claude-plugins (10 stars, last pushed today), licensed MIT. It adds 121 tokens to every session and 1,176 once invoked, about $0.0005 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-10-18.
Other skills, from other repositories
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
plugin-architecture-patterns
Design, implement, or diagnose Xberg plugin traits, typed registries, priority collisions, lifecycle, native extractors, and Alef-generated Python plugin bridges. Load for plugin-system work, not ordinary extractor parsing.
test-corpus
The testdocuments submodule is a bucket-fetched fixture corpus that is not committed. This skill covers readtestfixture, missing fixtures, valid A/B controls, and submodule push order. Load before running Rust tests on a fresh clone, setting up an A/B control, adding a fixture-backed test, or diagnosing…
stack-trace-python-probe
Internal helper for meta-stack-trace-investigator. Use when a Python traceback needs Python-specific root-cause checks, pytest reproducer guidance, and defensive patch targets.
memory-optimization
Optimize Python code for reduced memory usage and improved memory efficiency. Use when asked to reduce memory footprint, fix memory leaks, optimize data structures for memory, handle large datasets efficiently, or diagnose memory issues. Covers object sizing, generator patterns, efficient data structures, and memory…
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).