agentmods.dev

pytest.fix_local_tests

pytest.fix_local_tests is a skill for Claude Code from gpsaggese/helpers. It costs 7 tokens per session (785 once invoked), scanned A, original, Apache-2.0.

A test-failure investigation workflow for pytest, a Python testing tool, that finds the cause of failed local tests and fixes the code.

In plain words
What is it for?
Use it to run failing tests, collect the failures, inspect the relevant code, and apply fixes.
Why use it?
It turns a failing test or reproduction script into a focused diagnosis instead of requiring you to inspect every test manually.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

not rated 158repo +1 today A scan 7 tokens original Apache-2.0

Good fit Use it to run failing tests, collect the failures, inspect the relevant code, and apply fixes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/pytest.fix_local_tests
View source ↗ 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 pytest.fix_local_tests
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.

agentmods badge for pytest.fix_local_tests

README.md
[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/pytest.fix_local_tests/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/pytest.fix_local_tests)
Your own site
<a href="https://agentmods.dev/skills/gpsaggese/helpers/pytest.fix_local_tests"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/pytest.fix_local_tests/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.

agentmods 80×15 button for pytest.fix_local_tests

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/pytest.fix_local_tests"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/pytest.fix_local_tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 785 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.00785
Opus 5.5 $0.00003 $0.00314
Sonnet 5.5 $0.00001 $0.00157
Haiku 4.5 $0.00001 $0.00078

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

Security

Grade A, and why

pytest.fix_local_tests 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/pytest.fix_local_tests/SKILL.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Goal

  • Given info about failed tests <FAILURE_INFO>, run the tests, find the root cause, and fix them

Workflow

Run Tests

  • The input <FAILURE_INFO> can be:

    • A failing pytest test
      • E.g., dev_scripts_helpers/documentation/test/test_notes_to_pdf.py
    • A repro generated by pytest_failed_multi_build.py
      • E.g., tmp.pytest_failed_multi_build.repro.sh

  • Gather information about the failing tests by:

    • Reading the code
    • Inspecting the content of <FAILURE_INFO>
    • Running the tests locally, if needed
      • E.g., 
        > pytest_log `<FAILURE_INFO>`
> tmp.pytest_failed_multi_build.repro.sh

Analyze Failures

  • Read .claude/skills/pytest.rules.md to learn how to diagnose issues

  • Collect the failing tests from the run

    > i pytest_failed
...
Failed tests: 25/7
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_actions::test1
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_actions::test2
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_edge_cases::test1
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_edge_cases::test2
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_edge_cases::test3
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_edge_cases::test4
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_filters::test1
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_filters::test2
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_filters::test3
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_filters::test4
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_filters::test5
...
13:07:36 - WARN  lib_tasks_pytest.py pytest_failed:1745                 To run the failed tests run: tmp.pytest_failed.sh
...

Read the full file on GitHub · 78 lines

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.

  1. yesterday First seen · 78 lines · 7 tokens per session scan A b1a59217ada7

Subscribe to this mod's changes

pytest.fix_local_tests is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 7 tokens to every session and 785 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.

DebuggingTestingUnit testing
Related

pytest.fix_local_tests compared with skills from other repositories

pytest.fix_local_tests next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pytest.fix_local_testsgpsaggese/helpersSkill158todayApache-2.0A7Claude Code
testinggarrytan/gbrainSkill32ktodayMITA63Claude Code
verifyYeachan-Heo/oh-my-claudecodeSkill41ktodayMITA12Claude Code
detect-static-dependenciesdotnet/skillsSkill5.8ktodayMITA135Claude Code
testing-blocksadobe/skillsSkill319todayApache-2.0A61Claude Code
dart-downstream-fixdartsim/dartSkill1.2ktodayBSD-2-ClauseA25Claude Code
experiment-iterative-coderEvoScientist/EvoSkillsSkill48610d agoApache-2.0A145Claude Code