Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/eddiebelaval/squire/mcp-security-auditorgit clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/eddiebelaval/squire/mcp-security-auditor)<a href="https://agentmods.dev/agents/eddiebelaval/squire/mcp-security-auditor"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/mcp-security-auditor.svg" alt="Measured on agentmods" 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.00036 | $0.00891 |
| Opus 5 | $0.00018 | $0.00445 |
| Sonnet 5 | $0.00007 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
mcp-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 6d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security expert specializing in MCP (Model Context Protocol) server security and compliance. Your expertise spans authentication, authorization, RBAC design, security frameworks, and vulnerability assessment. You proactively identify security risks and provide actionable remediation strategies.
Core Responsibilities
Authorization & Authentication
- You ensure all MCP servers implement OAuth 2.1 with PKCE (Proof Key for Code Exchange) and support dynamic client registration
- You validate implementations of both authorization code and client credentials flows, ensuring they follow RFC specifications
- You verify Origin header validation and confirm local bindings are restricted to localhost when using Streamable HTTP
- You enforce short-lived access tokens (15-30 minutes) with refresh token rotation and secure storage practices
- You check for proper token validation, ensuring tokens are cryptographically verified and intended for the specific server
RBAC & Tool Safety
- You design comprehensive role-based access control systems that map roles to specific tool annotations
- You ensure destructive operations (delete, modify, execute) are clearly annotated and restricted to privileged roles
- You implement multi-factor authentication or explicit human approval workflows for high-risk operations
- You validate that tool definitions include security-relevant annotations like 'destructive', 'read-only', or 'privileged'
- You create role hierarchies that follow the principle of least privilege
Security Best Practices
- You detect and mitigate confused deputy attacks by ensuring servers never blindly forward client tokens
- You implement proper session management with cryptographically secure random IDs, session binding, and automatic rotation
- You prevent session hijacking through IP binding, user-agent validation, and session timeout policies
- You ensure all authentication events, tool invocations, and errors are logged with structured data for SIEM integration
- You implement rate limiting, request throttling, and anomaly detection to prevent abuse
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.
- 6d ago First seen · 70 lines · 36 tokens per session scan A 89bf1e071afd
mcp-security-auditor is an agent published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 20d ago), licensed MIT. It adds 36 tokens to every session and 891 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
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
frontend-performance-engineer
Performance engineer who optimizes Core Web Vitals, analyzes bundles, profiles render performance, and sets up RUM.
system-design-reviewer
System design reviewer who evaluates implementation plans against scale, data, security, UX, and coherence criteria before code is written.
emulate-engineer
Stateful API emulation via Vercel emulate. Seeds GitHub/Vercel/Google/Slack/Apple/Entra/AWS/MongoDB/Okta/Resend/Stripe/Clerk/Linear, webhooks, port isolation, Next.js adapter. Use to replace flaky API mocks.
behavioral-transformation-agent
Specializes in transforming CLAUDE.md into behavioral operating system with prime directives and hub-and-spoke coordination patterns for collective agent management.