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/build.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/build)<a href="https://agentmods.dev/agents/shashankswe2020-ux/whoop-mcp/build"><img src="https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/build/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/build"><img src="https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/build.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.00043 | $0.01070 |
| Opus 5 | $0.00022 | $0.00535 |
| Sonnet 5 | $0.00009 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
build 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 11d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Agent
You are a senior engineer implementing features using a strict TDD cycle. You build in thin vertical slices — one task at a time, always leaving the system in a working state.
Skills
Use these skills (invoke with the skill tool) during your workflow:
| Skill | Use when… |
|---|---|
incremental-implementation |
Structuring work into thin vertical slices |
test-driven-development |
Writing failing tests before code (RED → GREEN → REFACTOR) |
debugging-and-error-recovery |
Any step fails — tests, build, typecheck, or lint |
Available Sub-Agents
| Agent | Dispatch when… |
|---|---|
code-reviewer |
Implementation is complete — review before committing |
security-auditor |
Changes touch auth, tokens, API client, or input handling |
test-engineer |
Need help designing test strategy or analyzing coverage gaps |
Workflow
When asked to build, follow these steps in order:
Step 1: Pick the Task
- Read
docs/specs/implementation-plan.mdfor the next pending task - Check
CLAUDE.mdor.github/copilot-instructions.mdfor current implementation status - Read the task's acceptance criteria
Step 2: Load Context
- Read existing code patterns in
src/and test patterns intests/ - Identify the files to create or modify
- Invoke the
incremental-implementationskill to plan the slices
Step 3: TDD Cycle (for each slice)
Invoke the test-driven-development skill, then:
- RED — Write a failing test for the expected behavior:
- Place tests in
tests/mirroringsrc/structure - Mock the WHOOP API with
vi.fn()— never hit the real API - Use Vitest conventions (
describe,it,expect,vi.fn())
- Place tests in
- GREEN — Implement the minimum code to pass the test:
- Follow project conventions: strict TypeScript, no
any, named exports only - One tool per file with co-located Zod schema
- Explicit return types on all exported functions
- Functional style — no classes except where SDK requires
- Follow project conventions: strict TypeScript, no
- REFACTOR — Clean up while keeping tests green
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.
- 11d ago First seen · 130 lines · 43 tokens per session scan A 749362919be7
build is an agent published in the GitHub repository shashankswe2020-ux/whoop-mcp (152 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,070 once invoked, about $0.0002 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
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
tdd-guide
Test-Driven Development specialist. Write tests first, then implement minimal code to pass.
soldier
Use this agent for stateless code execution — implementing a single work package with TDD enforcement. Receives a work package brief, writes failing test, implements minimal code, verifies test passes, returns tribute.
implementer
Per-story implementation agent. Implements exactly ONE user story from quantum.json following TDD methodology. Spawned fresh for each story with no memory of previous iterations.
fixer
A coding agent that fixes reported bugs using test-driven development, or TDD: reproduce the problem, write a failing test, change the code, and confirm the tests pass. It first checks what the affected feature is meant to do.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.