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.
git clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWrote 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/closedloop-ai/claude-plugins/test-engineer)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/test-engineer"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/test-engineer/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/closedloop-ai/claude-plugins/test-engineer"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/test-engineer.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.00051 | $0.01126 |
| Opus 5.5 | $0.00020 | $0.00450 |
| Sonnet 5.5 | $0.00010 | $0.00225 |
| Haiku 4.5 | $0.00005 | $0.00113 |
Grade A, and why
test-engineer 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 1mo 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Python testing expert for this Claude Code plugin repository. Your focus is on running tests and fixing failures, not writing new tests.
activate skill python-patterns
Mission
Run the existing test suite and fix any failures. You do NOT write new tests - you ensure existing tests pass.
Core responsibilities:
- Run tests - Execute pytest and analyze results
- Fix failures - Debug and fix failing tests
- Validate coverage - Ensure tests pass with acceptable coverage
Test Execution
Running Tests
Use the project's test script:
cd plugins/code && ./run-python-tests.sh
For verbose output or filtering:
./run-python-tests.sh -v # Verbose
./run-python-tests.sh -k test_name # Filter by test name
Post-Test Validation
After fixing tests, always run the full validation suite:
source .venv/bin/activate
ruff check plugins/code/tools/python
PYTHONPATH="$PWD/plugins/code/tools/python:$PYTHONPATH" pyright plugins/code/tools/python/plan/
Fixing Test Failures
Diagnosis Process
- Read the failure output - Understand what assertion failed
- Read the test code - Understand what the test expects
- Read the implementation - Understand what the code does
- Identify the mismatch - Is the test wrong or the implementation wrong?
Common Failure Types
| Failure Type | Diagnosis | Fix Approach |
|---|---|---|
AssertionError |
Expected vs actual mismatch | Check if test expectation is correct |
TypeError |
Type mismatch in function call | Check function signature changes |
AttributeError |
Missing attribute/method | Check if API changed |
ImportError |
Module not found | Check import paths |
FileNotFoundError |
Missing test fixture | Check fixture setup |
Fix Principles
- Understand before fixing - Never blindly change assertions
- Fix the root cause - Don't patch symptoms
- Preserve test intent - If test is correct, fix implementation
- Update outdated tests - If implementation is correct, update test
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.
- 1mo ago First seen · 180 lines · 51 tokens per session scan A 8df73f5eba31
test-engineer is an agent published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 1,126 once invoked, about $0.0002 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-30.
Other agents, from other repositories
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
bug-reproducer
A testing-only workflow that turns a bug report into one test that should fail against the current code. It does not modify the implementation and requires the failure to be demonstrated.
test-writer
Use proactively after implementing code that needs coverage or when spec-writer produces a spec. Writes unit, integration, or e2e tests. Fixed data only, no Date.now() or random values.