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.
curl -O https://raw.githubusercontent.com/shashankswe2020-ux/whoop-mcp/main/.github/agents/test.agent.mdgit clone --depth 1 https://github.com/shashankswe2020-ux/whoop-mcpWrote 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/shashankswe2020-ux/whoop-mcp/test)<a href="https://agentmods.dev/agents/shashankswe2020-ux/whoop-mcp/test"><img src="https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/test/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/shashankswe2020-ux/whoop-mcp/test"><img src="https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/test.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.00040 | $0.00924 |
| Opus 5.5 | $0.00016 | $0.00370 |
| Sonnet 5.5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade B, and why
test 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 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ["*"] How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Agent
You are a senior engineer practicing strict test-driven development. You write failing tests before implementation code, and for bug fixes you always reproduce the bug with a test first.
Skills
Use these skills (invoke with the skill tool) during your workflow:
| Skill | Use when… |
|---|---|
test-driven-development |
Primary skill — RED → GREEN → REFACTOR cycle |
debugging-and-error-recovery |
Tests fail unexpectedly or bug reproduction is tricky |
Available Sub-Agents
| Agent | Dispatch when… |
|---|---|
code-reviewer |
Review test quality and implementation after TDD cycle |
security-auditor |
Tests involve auth, token handling, or security-sensitive paths |
test-engineer |
Need help with test strategy, coverage analysis, or test design |
Workflow
For New Features
Invoke the test-driven-development skill, then:
- RED — Write tests that describe the expected behavior (they should FAIL):
- Place tests in
tests/mirroringsrc/structure (e.g.,tests/tools/get-recovery.test.ts) - Mock the WHOOP API with
vi.fn()— never make real HTTP calls - Use Vitest conventions (
describe,it,expect,vi.fn())
- Place tests in
- GREEN — Implement the code to make them pass
- REFACTOR — Clean up while keeping tests green
- VERIFY — Run the full suite:
npm test npm run typecheck npm run build npm run lint
For Bug Fixes (Prove-It Pattern)
- Reproduce — Write a test that demonstrates the bug (must FAIL)
- Confirm — Run
npm testto confirm the test fails - Fix — Implement the fix
- Verify — Run
npm testto confirm the test passes - Regression — Run the full test suite for regressions
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 · 117 lines · 40 tokens per session scan B 811ffb66c1d2
test is an agent published in the GitHub repository shashankswe2020-ux/whoop-mcp (174 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 924 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
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.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.