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 agentmods add skills/yxhpy/openuser/auto-testnpx skills add yxhpy/openuser --skill auto-testgit clone --depth 1 https://github.com/yxhpy/openuserWhat 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 | $0.00037 | $0.01360 |
| Opus 5 | $0.00018 | $0.00680 |
| Sonnet 5 | $0.00007 | $0.00272 |
| Haiku 4.5 | $0.00004 | $0.00136 |
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 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.
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:
- Detect Changes - Identify which files were modified
- Run Relevant Tests - Run tests for the modified modules
- Check Coverage - Ensure 100% coverage (
pytest --cov --cov-fail-under=100) - Report Results - Display test results and coverage report
- Handle Failures - If tests fail, provide debugging guidance
- 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
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.
- 2d ago First seen · 203 lines · 37 tokens per session scan A dbf64a92fa71
auto-test is a skill published in the GitHub repository yxhpy/openuser (2 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 1,360 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.