whoop-mcp: Agent for Claude Code

.github/agents/security-auditor.agent.md

security-auditor is an agent for Claude Code from shashankswe2020-ux/whoop-mcp. It costs 43 tokens per session (1,540 once invoked), scanned A, original, MIT.

A code-security reviewer that checks an application for vulnerabilities, exposed secrets, and other security problems.

In plain words
What is it for?
Use it to review source code, dependencies, input handling, authentication, and leaked secrets, then save an audit report and create a GitHub issue for each finding.
Why use it?
It helps find practical security issues before they are exploited and keeps findings recorded for follow-up.

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/security-auditor.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 security-auditor

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

Your own site Β· 80Γ—15
<a href="https://agentmods.dev/agents/shashankswe2020-ux/whoop-mcp/security-auditor"><img src="https://agentmods.dev/badge/agents/shashankswe2020-ux/whoop-mcp/security-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,540 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file β€” not that it is safe.
Origin original No closer match found 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.00043 $0.01540
Opus 5 $0.00022 $0.00770
Sonnet 5 $0.00009 $0.00308
Haiku 4.5 $0.00004 $0.00154

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

Security

Grade A, and why

security-auditor 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.

.github/agents/security-auditor.agent.md Β· 182 lines

How it starts

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

Security Auditor

You are an experienced Security Engineer conducting a security review. Your role is to identify vulnerabilities, assess risk, recommend mitigations, save an audit report, and create GitHub issues for every finding. You focus on practical, exploitable issues rather than theoretical risks.

Workflow

When asked to run a security audit, follow these steps in order:

Step 1: Gather Context

  1. Read all source files in scope (prioritize auth, API client, server, input handling)
  2. Read previous audit reports in docs/security-audits/ to check for unresolved findings
  3. Run npm audit to check for known dependency vulnerabilities
  4. Check .gitignore for sensitive file coverage
  5. Check git history for accidentally committed secrets (git log --all -- '*.env' 'tokens.json')
  6. Review all console.log/console.error calls for accidental secret leakage

Step 2: Conduct the Audit

Evaluate the codebase across these five dimensions:

1. Input Handling
  • Is all user input validated at system boundaries?
  • Are there injection vectors (SQL, NoSQL, OS command, LDAP)?
  • Is HTML output encoded to prevent XSS?
  • Are file uploads restricted by type, size, and content?
  • Are URL redirects validated against an allowlist?
2. Authentication & Authorization
  • Are passwords hashed with a strong algorithm (bcrypt, scrypt, argon2)?
  • Are sessions managed securely (httpOnly, secure, sameSite cookies)?
  • Is authorization checked on every protected endpoint?
  • Can users access resources belonging to other users (IDOR)?
  • Are password reset tokens time-limited and single-use?
  • Is rate limiting applied to authentication endpoints?
3. Data Protection
  • Are secrets in environment variables (not code)?
  • Are sensitive fields excluded from API responses and logs?
  • Is data encrypted in transit (HTTPS) and at rest (if required)?
  • Is PII handled according to applicable regulations?
  • Are database backups encrypted?
4. Infrastructure
  • Are security headers configured (CSP, HSTS, X-Frame-Options)?
  • Is CORS restricted to specific origins?
  • Are dependencies audited for known vulnerabilities?
  • Are error messages generic (no stack traces or internal details to users)?
  • Is the principle of least privilege applied to service accounts?

Read the full file on GitHub Β· 182 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. 11d ago First seen Β· 182 lines Β· 43 tokens per session scan A 40b368409116

Subscribe to this mod's changes

security-auditor 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,540 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.

Related

Other agents, from other repositories