openuser: Skill for Claude Code

.claude/skills/auto-test/SKILL.md

auto-test is a skill for Claude Code from yxhpy/openuser. It costs 37 tokens per session (1,360 once invoked), scanned A, original, MIT.

An automatic testing rule for Python projects that watches for changes in the src directory and checks test coverage.

In plain words
What is it for?
It detects changed files, runs relevant or full pytest suites, checks for 100% coverage, reports failures, and records results in project memory.
Why use it?
It catches regressions after code changes and enforces the project's requirement for complete test coverage before work is considered ready.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is yxhpy/openuser's own configuration. It tells Claude Code how to work on openuser itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything openuser configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/yxhpy/PycharmProjects/openuser.

Reuse

Borrowing it

Nothing to install: this file belongs to yxhpy/openuser. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/yxhpy/openuser/main/.claude/skills/auto-test/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/yxhpy/openuser

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 auto-test

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/yxhpy/openuser/auto-test"><img src="https://agentmods.dev/badge/skills/yxhpy/openuser/auto-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,360 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.00037 $0.01360
Opus 5.5 $0.00015 $0.00544
Sonnet 5.5 $0.00007 $0.00272
Haiku 4.5 $0.00004 $0.00136

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

Security

Grade A, and why

auto-test 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 2mo 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.

.claude/skills/auto-test/SKILL.md · 203 lines

How it starts

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

Auto Test Skill

This skill automatically runs tests after code changes to ensure 100% test coverage.

Trigger Conditions

This skill is triggered when:

  • Any Python file in src/ is modified
  • User explicitly requests to run tests
  • After completing a feature implementation
  • Before committing code

Behavior

When triggered, this skill will:

  1. Detect Changes - Identify which files were modified
  2. Run Relevant Tests - Run tests for the modified modules
  3. Check Coverage - Ensure 100% coverage (pytest --cov --cov-fail-under=100)
  4. Report Results - Display test results and coverage report
  5. Handle Failures - If tests fail, provide debugging guidance
  6. Update Status - Record test results in project memory

Test Commands

Run All Tests

pytest --cov --cov-fail-under=100

Run Specific Test Suite

pytest tests/unit/ --cov=src
pytest tests/integration/ --cov=src
pytest tests/e2e/ --cov=src

Run Tests for Specific Module

pytest tests/unit/test_plugin_manager.py --cov=src.core.plugin_manager

Generate HTML Coverage Report

pytest --cov --cov-report=html
open htmlcov/index.html

Coverage Requirements

  • Minimum Coverage: 100%
  • Branch Coverage: Required
  • Function Coverage: Required
  • Line Coverage: Required

Test Structure

tests/
├── unit/                  # Unit tests (fast, isolated)
│   ├── test_plugin_manager.py
│   ├── test_agent_manager.py
│   └── test_config_manager.py
├── integration/           # Integration tests (multiple components)
│   ├── test_api_endpoints.py
│   ├── test_plugin_integration.py
│   └── test_agent_integration.py
└── e2e/                   # End-to-end tests (full workflows)
    ├── test_digital_human_creation.py
    ├── test_plugin_hot_reload.py
    └── test_agent_self_update.py

Test Patterns

Unit Test Example

# tests/unit/test_plugin_manager.py
import pytest
from src.core.plugin_manager import PluginManager

def test_plugin_manager_init():
    """Test PluginManager initialization"""
    pm = PluginManager()
    assert pm is not None
    assert pm.plugins == {}

def test_load_plugin():
    """Test loading a plugin"""
    pm = PluginManager()
    pm.load_plugin("test-plugin")
    assert "test-plugin" in pm.plugins

def test_reload_plugin():
    """Test hot-reloading a plugin"""
    pm = PluginManager()
    pm.load_plugin("test-plugin")
    pm.reload_plugin("test-plugin")
    assert "test-plugin" in pm.plugins

Read the full file on GitHub · 203 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. 2mo ago First seen · 203 lines · 37 tokens per session scan A dbf64a92fa71

Subscribe to this mod's changes

auto-test is a skill published in the GitHub repository yxhpy/openuser (2 stars, last pushed 8mo ago), licensed MIT. It adds 37 tokens to every session and 1,360 once invoked, about $0.0001 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-08-31.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens