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 besoeasy/open-skills --skill debug-order-sensitive-pytestgit clone --depth 1 https://github.com/besoeasy/open-skillsWrote 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/besoeasy/open-skills/debug-order-sensitive-pytest)<a href="https://agentmods.dev/skills/besoeasy/open-skills/debug-order-sensitive-pytest"><img src="https://agentmods.dev/badge/skills/besoeasy/open-skills/debug-order-sensitive-pytest/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/besoeasy/open-skills/debug-order-sensitive-pytest"><img src="https://agentmods.dev/badge/skills/besoeasy/open-skills/debug-order-sensitive-pytest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00083 | $0.02192 |
| Opus 5 | $0.00042 | $0.01096 |
| Sonnet 5 | $0.00017 | $0.00438 |
| Haiku 4.5 | $0.00008 | $0.00219 |
Grade A, and why
debug-order-sensitive-pytest 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 7d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Order-Sensitive Pytest Failures
Find and fix tests that pass on their own but fail when pytest runs in a different order. The suite is green again only after every leaked-global-state polluter is fixed and both the shuffled and the normal runs pass.
Quick quality checklist
- Repro order is pinned with a fixed seed and printed so any failure is reproducible
- Always bisect with the failing target test appended to every slice (a failing window can contain multiple polluters)
- Instrumented runs are only hints — always confirm on clean runs
- No private data, paths, or project-specific test names in this skill
When to use
- A test fails only in the full suite but passes standalone with
pytest <file>orpytest <nodeid> - A CI job that randomizes test order (pytest-randomly, custom shuffle) is flaky
- You suspect a test mutates
sys.modules, reloads a module, or mutates a shared module-level singleton without restoring it
Required tools / APIs
- Python 3.8+ and pytest (no external API)
- Optional: a shuffling runner (pytest-randomly, or a local seeded-shuffle plugin, described below)
Steps
1. Reproduce with a fixed-seed shuffle
Pin the order so every bisection uses the exact same failing sequence. Use pytest-randomly:
pip install pytest-randomly
python -m pytest -q --randomly-seed=42 -p no:cacheprovider --tb=no | tee order.log
Or, for a repo that already has a seeded-shuffle runner (e.g. tests/run_order_report.py --seed 42), use it. If neither exists, add a tiny local plugin that shuffles collection with a fixed seed:
# shuffle42.py (load with: python -m pytest -p shuffle42 ...)
import random
def pytest_collection_modifyitems(items):
random.Random(42).shuffle(items)
Record the failing nodeids from the log. The seed must be printed/stored so the order is reproducible.
2. Dump the shuffled order to a file
Every bisection slice must come from the same shuffled order. The shuffle must be re-applied deterministically to the same collected list, so dump the exact order once:
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.
- 7d ago First seen · 179 lines · 83 tokens per session scan A 14d8627fb74a
debug-order-sensitive-pytest is a skill published in the GitHub repository besoeasy/open-skills (132 stars, last pushed 7d ago), licensed MIT. It adds 83 tokens to every session and 2,192 once invoked, about $0.0004 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-09-05.
Other skills, from other repositories
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
agent-debug-fixer
A Chinese-language debugging and repair workflow for software problems. It investigates errors, failed tests, broken pages, or behavior that does not match expectations, then makes a minimal fix.
qa
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a…
terraform-test
Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, or troubleshooting Terraform test…
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.