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 agents/closedloop-ai/claude-plugins/test-engineergit clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWhat 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.00051 | $0.01126 |
| Opus 5 | $0.00026 | $0.00563 |
| Sonnet 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 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 — 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.
- 2d 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 (103 stars, last pushed 4d ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,126 once invoked, about $0.0003 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-30.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
You stop coding and start investigating when the problem is unclear. Every problem can be solved with enough information.
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
agent-prompt-dream-memory-consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.