What is coding.fix_pyright?

A task that runs Pyright on Python files and fixes the type-related problems it reports. Type checking finds places where values may be used with the wrong kind of data.

Use it to inspect Pyright output, correct Python type issues, and verify that the affected tests still pass.

It reduces reported type errors without changing the program's behavior. It compares the results before and after the fixes and checks related unit tests.

coding.fix_pyright — Skill for Claude Code by gpsaggese/helpers

Install

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.

Any agent

npx skills add gpsaggese/helpers --skill coding.fix_pyright

Clone the repo

git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/coding.fix_pyright/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/coding.fix_pyright)

Your own site

<a href="https://agentmods.dev/skills/gpsaggese/helpers/coding.fix_pyright"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/coding.fix_pyright/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gpsaggese/helpers/coding.fix_pyright"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/coding.fix_pyright.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 264 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00012	$0.00264
Opus 5.5	$0.00005	$0.00106
Sonnet 5.5	$0.00002	$0.00053
Haiku 4.5	$0.00001	$0.00026

Measured yesterday against content hash 6389a2a925a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coding.fix_pyright 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 yesterday.

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.

.claude/skills/coding.fix_pyright/SKILL.md · 30 lines

What it actually says

Goal

Given a list of files <FILES>, run pyright on them and fix the reported lints without changing behavior.

Workflow

Run `pyright`

Run pyright on the <FILES> generating a file tmp.pyright_before.txt
Summarize the types of issues and how many of them are present

Fix Lints From `pyright`

Read tmp.pyright_before.txt
Fix the lints without changing the behavior of the code
If there are tests in test/test_<FILE>.py, run the tests to make sure they are still passing
- E.g., for helpers/haws.py run helpers/test/test_haws.py

Run `pyright` After the Fixes

Run pyright on the <FILES> generating a file tmp.pyright_after.txt
Summarize the types of issues and how many of them are present

Verification

Confirm tmp.pyright_after.txt shows fewer or no issues compared to tmp.pyright_before.txt
Confirm the corresponding unit tests still pass

Changes

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.

yesterday First seen · 30 lines · 12 tokens per session scan A 6389a2a925a2

Subscribe to this mod's changes

coding.fix_pyright is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 264 once invoked, about $0.0000 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-11-06.

Languages Python Testing Unit testing

coding.fix_pyright next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
coding.fix_pyrightgpsaggese/helpers	Skill	158	today	Apache-2.0	A	12	Claude Code
temporal-python-testingwshobson/agents	Skill	42k	2d ago	MIT	A	45	Claude Code
python-testingmicrosoft/agent-framework	Skill	15k	today	MIT	A	29	Claude Code, Codex
adk-verify-snippetsgoogle/adk-python	Skill	22k	today	Apache-2.0	C	149	Claude Code, Codex
adk-setupgoogle/adk-python	Skill	22k	today	Apache-2.0	C	146	Claude Code
test-generatorvstorm-co/pydantic-deepagents	Skill	1.1k	8d ago	MIT	A	12	Claude Code, Codex
kb-python-developmentCommunity-Access/accessibility-agents	Skill	436	today	MIT	A	39	Claude Code, Codex