ele-test-runner

A short guide for checking an EleSync Python project with tests and code-quality tools. It explains commands for running all tests, selected tests, linters, and formatters.

In plain words
What is it for?
Use it to install development dependencies, run `pytest`, run a single test, check code with Ruff, and format the code.
Why use it?
It removes the need to remember the project’s validation commands or guess which checks to run before sharing changes.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/darknodebros/elesync/ele-test-runner
Any agent
npx skills add darknodebros/EleSync --skill ele-test-runner
Clone the repo
git clone --depth 1 https://github.com/darknodebros/EleSync

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 435 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00435
Opus 5 $0.00000 $0.00217
Sonnet 5 $0.00000 $0.00087
Haiku 4.5 $0.00000 $0.00044

Measured 2d ago against content hash 4d8e36e9cc16, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ele-test-runner 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 2d 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.

.github/skills/ele-test-runner/SKILL.md · 39 lines

What it actually says

++ Name: ele-test-runner

Description: A small, focused skill that documents how to run tests, linters, and common verifier commands for EleSync. Use this to quickly orient agents (or humans) on the minimal commands and expectations for validating changes.

Purpose:

  • Give concise, copy-paste commands to run tests and linters.
  • Explain when and how to run targeted tests.
  • Provide quick troubleshooting steps for common failures.

Where it lives:

  • This file: .github/skills/ele-test-runner/SKILL.md

Commands (copy-paste):

  • Dev install: pip install -e .[dev] or pip install ".[dev]"
  • Run full test suite: pytest
  • Run a single test file: pytest tests/test_module.py
  • Run a single test function: pytest tests/test_module.py::test_function
  • Run linters/formatters: ruff check . and ruff format .

When to run:

  • Before opening a PR: run pytest (or targeted tests for your changes) and ruff check ..
  • For CI-like quick checks locally: run pytest -q and ruff check ..

Expectations / outputs:

  • Passing tests: exit code 0 and summary == X passed.
  • Failing tests: pytest shows failing trace and assertion — add or update tests and fix code or tests as appropriate.
  • Linting: ruff check lists issues; run ruff format . to fix formatting, then re-run ruff check.

Troubleshooting:

  • If tests fail due to missing optional dependencies, re-run with dev extras: pip install ".[dev]".
  • For environment-specific errors, run the failing test individually to get a focused traceback.
  • If a test appears flaky, mark with @pytest.mark.flaky or open an issue and add a regression test.

Notes for agents:

  • Prefer minimal, well-tested changes. Add a test for bug fixes or behavior changes.
  • Do not modify CI configuration in this skill; link to pyproject.toml for tooling details.
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. 2d ago First seen · 39 lines · 0 tokens per session scan A 4d8e36e9cc16

Subscribe to this mod's changes

ele-test-runner is a skill published in the GitHub repository darknodebros/EleSync (4 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 435 tokens. 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.