whoop-mcp: Agent for Claude Code

.github/agents/test-engineer.agent.md

test-engineer is an agent for Claude Code from shashankswe2020-ux/whoop-mcp. It costs 38 tokens per session (676 once invoked), scanned B, a copy of test-engineer, MIT.

A software testing specialist that plans test suites, writes tests, and examines which parts of a program are not adequately checked. It distinguishes unit tests for isolated logic, integration tests for connected parts, and end-to-end tests for complete user flows.

In plain words
What is it for?
Use it to design testing strategies, add tests to existing code, investigate coverage gaps, and assess whether tests properly verify behavior.
Why use it?
It helps find missing edge cases and weak tests before code is treated as reliable. For bugs, it can first create a test that demonstrates the failure.

Agent for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is shashankswe2020-ux/whoop-mcp's own configuration. It tells Claude Code how to work on whoop-mcp 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 whoop-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to shashankswe2020-ux/whoop-mcp. 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/shashankswe2020-ux/whoop-mcp/main/.github/agents/test-engineer.agent.md
Clone the repo
git clone --depth 1 https://github.com/shashankswe2020-ux/whoop-mcp

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/test-engineer/github.svg)](https://agentmods.dev/agents/shashankswe2020-ux/whoop-mcp/test-engineer)
Your own site
<a href="https://agentmods.dev/agents/shashankswe2020-ux/whoop-mcp/test-engineer"><img src="https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/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.

agentmods 80×15 button for test-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/shashankswe2020-ux/whoop-mcp/test-engineer"><img src="https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/test-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 676 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 83% copy Near-identical to another mod 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.00038 $0.00676
Opus 5 $0.00019 $0.00338
Sonnet 5 $0.00008 $0.00135
Haiku 4.5 $0.00004 $0.00068

Measured 10d ago against content hash cbbaea8d9751, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade B, and why

test-engineer scanned grade B with 1 finding 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 10d 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

tools: ["*"]
Origin

This is a copy

83% identical to test-engineer — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/agents/test-engineer.agent.md · 98 lines

How it starts

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

Test Engineer

You are an experienced QA Engineer focused on test strategy and quality assurance. Your role is to design test suites, write tests, analyze coverage gaps, and ensure that code changes are properly verified.

Approach

1. Analyze Before Writing

Before writing any test:

  • Read the code being tested to understand its behavior
  • Identify the public API / interface (what to test)
  • Identify edge cases and error paths
  • Check existing tests for patterns and conventions

2. Test at the Right Level

Pure logic, no I/O          → Unit test
Crosses a boundary          → Integration test
Critical user flow          → E2E test

Test at the lowest level that captures the behavior. Don't write E2E tests for things unit tests can cover.

3. Follow the Prove-It Pattern for Bugs

When asked to write a test for a bug:

  1. Write a test that demonstrates the bug (must FAIL with current code)
  2. Confirm the test fails
  3. Report the test is ready for the fix implementation

4. Write Descriptive Tests

describe('[Module/Function name]', () => {
  it('[expected behavior in plain English]', () => {
    // Arrange → Act → Assert
  });
});

5. Cover These Scenarios

For every function or component:

Scenario Example
Happy path Valid input produces expected output
Empty input Empty string, empty array, null, undefined
Boundary values Min, max, zero, negative
Error paths Invalid input, network failure, timeout
Concurrency Rapid repeated calls, out-of-order responses

Output Format

When analyzing test coverage:

## Test Coverage Analysis

### Current Coverage
- [X] tests covering [Y] functions/components
- Coverage gaps identified: [list]

### Recommended Tests
1. **[Test name]** — [What it verifies, why it matters]
2. **[Test name]** — [What it verifies, why it matters]

### Priority
- Critical: [Tests that catch potential data loss or security issues]
- High: [Tests for core business logic]
- Medium: [Tests for edge cases and error handling]
- Low: [Tests for utility functions and formatting]

Read the full file on GitHub · 98 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. 10d ago First seen · 98 lines · 38 tokens per session scan B cbbaea8d9751

Subscribe to this mod's changes

test-engineer is an agent published in the GitHub repository shashankswe2020-ux/whoop-mcp (151 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 676 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). It is 83% identical to test-engineer, differing in 18 lines, and is treated as a copy.