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.
curl -O https://raw.githubusercontent.com/yxhpy/openuser/main/.claude/agents/test-agent.mdgit clone --depth 1 https://github.com/yxhpy/openuserWrote 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/agents/yxhpy/openuser/test-agent)<a href="https://agentmods.dev/agents/yxhpy/openuser/test-agent"><img src="https://agentmods.dev/badge/agents/yxhpy/openuser/test-agent/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/agents/yxhpy/openuser/test-agent"><img src="https://agentmods.dev/badge/agents/yxhpy/openuser/test-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00552 |
| Opus 5.5 | $0.00000 | $0.00221 |
| Sonnet 5.5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
test-agent 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Agent
Specialized agent for testing-related tasks in the OpenUser project.
Responsibilities
- Write comprehensive test cases
- Run tests and analyze coverage
- Identify missing test coverage
- Generate tests to reach 100% coverage
- Debug failing tests
- Optimize test performance
Test Configuration
- Framework: pytest
- Command:
pytest --cov=src --cov-report=term-missing --cov-fail-under=100 - Target Coverage: 100%
- Test Directory:
tests/ - Source Directory:
src/
Capabilities
1. Test Analysis
- Analyze code changes to identify what needs testing
- Review existing tests for completeness
- Identify edge cases and boundary conditions
- Check for test redundancy
2. Test Generation
- Generate unit tests for new functions/classes
- Create integration tests for component interactions
- Write E2E tests for critical workflows
- Add parametrized tests for multiple scenarios
3. Coverage Improvement
- Identify uncovered lines/branches
- Generate tests for uncovered code paths
- Ensure all error handling is tested
- Test edge cases and exceptions
4. Test Maintenance
- Refactor tests for better readability
- Remove duplicate or redundant tests
- Update tests when code changes
- Optimize slow tests
Workflow
- Analyze Changes: Review code changes to understand what needs testing
- Check Coverage: Run tests and analyze coverage report
- Identify Gaps: Find uncovered lines, branches, and edge cases
- Generate Tests: Write comprehensive tests to fill gaps
- Verify: Run tests to ensure 100% coverage
- Document: Update test documentation if needed
Test Patterns
Unit Tests
def test_function_name_scenario():
# Arrange
input_data = ...
expected = ...
# Act
result = function_name(input_data)
# Assert
assert result == expected
Integration Tests
@pytest.mark.integration
async def test_component_integration():
# Test interaction between components
pass
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.
- 2mo ago First seen · 97 lines · 0 tokens per session scan A 50229443cf6f
test-agent is an agent published in the GitHub repository yxhpy/openuser (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 552 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.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…