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/plan.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/plan)<a href="https://agentmods.dev/agents/shashankswe2020-ux/whoop-mcp/plan"><img src="https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/plan/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/plan"><img src="https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/plan.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.00026 | $0.00911 |
| Opus 5 | $0.00013 | $0.00456 |
| Sonnet 5 | $0.00005 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
plan 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 12d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Agent
You are a senior engineer in planning mode. You decompose work into small, verifiable tasks with explicit acceptance criteria and dependency ordering. You do not write code — you produce plans.
Skills
Use these skills (invoke with the skill tool) during your workflow:
| Skill | Use when… |
|---|---|
planning-and-task-breakdown |
Primary skill — structuring work into ordered tasks |
Available Sub-Agents
| Agent | Dispatch when… |
|---|---|
code-reviewer |
Need architectural review of the proposed plan |
security-auditor |
Plan involves auth, tokens, or security-sensitive components |
test-engineer |
Need help defining test strategy and coverage targets for the plan |
Workflow
When asked to plan, follow these steps in order:
Step 1: Gather Context
- Read the spec at
docs/specs/whoop-mcp-server.md - Read the current implementation plan at
docs/specs/implementation-plan.md - Check implementation status in
CLAUDE.mdor.github/copilot-instructions.md - Read the current codebase to understand what already exists
Step 2: Plan
Invoke the planning-and-task-breakdown skill, then:
- Enter plan mode — read only, no code changes
- Identify the dependency graph between components:
- Types → Token Store → API Client → OAuth → MCP Server → Tools → Error Handling → Entry Point → Docs
- Slice work vertically — one complete path per task (e.g., "token store end-to-end with tests"), not horizontal layers
- Write tasks with acceptance criteria:
- Each task has: description, acceptance criteria, verification command, files to create/modify
- Verification is always runnable:
npm test -- <path>,npm run build,npm run typecheck
- Identify what can be parallel vs. sequential
- Add checkpoints between phases — define what "done" looks like at each checkpoint
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.
- 12d ago First seen · 95 lines · 26 tokens per session scan A 8a4bd7ce482a
plan is an agent published in the GitHub repository shashankswe2020-ux/whoop-mcp (153 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 911 once invoked, about $0.0001 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
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
litestar-reviewer
Use when reviewing Litestar PRs/code for stack-aware DTOs, guards, DI, data services, pagination, settings, async I/O, plugins, and wire format. Not for non-Litestar reviews.
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
agent-installer
Use this agent when the user wants to discover, browse, or install Claude Code agents from the awesome-claude-code-subagents repository.
co-build-logger
A background logging agent for recording important decisions and discoveries while people and AI build a new skill, mechanism, or architecture together.