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/security-auditor.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/security-auditor)<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.
<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>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.01540 |
| Opus 5.5 | $0.00017 | $0.00616 |
| Sonnet 5.5 | $0.00009 | $0.00308 |
| Haiku 4.5 | $0.00004 | $0.00154 |
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 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.
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 — 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
- Read all source files in scope (prioritize auth, API client, server, input handling)
- Read previous audit reports in
docs/security-audits/to check for unresolved findings - Run
npm auditto check for known dependency vulnerabilities - Check
.gitignorefor sensitive file coverage - Check git history for accidentally committed secrets (
git log --all -- '*.env' 'tokens.json') - Review all
console.log/console.errorcalls 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?
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 · 182 lines · 43 tokens per session scan A 40b368409116
security-auditor is an agent published in the GitHub repository shashankswe2020-ux/whoop-mcp (174 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,540 once invoked, about $0.0002 per session on Opus 5.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
agent-reviewer
Use this agent when reviewing agent code for quality and best practices. Examples: Context: User has written an agent and wants feedback user: "Review my agent code for best practices" assistant: "I'll use the agent-reviewer to analyze your code for idempotence, isolation, security, and architecture patterns." User…
kicad-design-review-agent
Performs a thorough hardware design review of a KiCAD project. Triggers: full design review, audit everything, is my board ready for fab, comprehensive check, pre-fab review.
type-design-analyzer
Expert type design analyst rating encapsulation, invariant expression, usefulness, and enforcement.
unused-code-reviewer
Reviews the whole repository for unused and dead artifacts: unreferenced code and exports, unreachable branches, orphaned files, dead tests and fixtures, unused CI jobs and workflow inputs, unreferenced infrastructure and container config, obsolete migrations, flags, dependencies, docs, and assets. Spawn when user…
code-reviewer
Reviews the codebase for correctness, style, patterns, and anti-patterns. Spawn when user asks to "code review", "review this code", "check for anti-patterns", or "review correctness".
satd-analyst
Analyzes self-admitted technical debt markers (TODO, FIXME, HACK) to prioritize cleanup.