Borrowing it
Nothing to install: this file belongs to op-enny/mcp-server-fakestore. 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/op-enny/mcp-server-fakestore/main/.claude/agents/api-security-audit.mdgit clone --depth 1 https://github.com/op-enny/mcp-server-fakestoreWrote 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/op-enny/mcp-server-fakestore/api-security-audit)<a href="https://agentmods.dev/agents/op-enny/mcp-server-fakestore/api-security-audit"><img src="https://agentmods.dev/badge/agents/op-enny/mcp-server-fakestore/api-security-audit/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/op-enny/mcp-server-fakestore/api-security-audit"><img src="https://agentmods.dev/badge/agents/op-enny/mcp-server-fakestore/api-security-audit.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.00034 | $0.00630 |
| Opus 5 | $0.00017 | $0.00315 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
api-security-audit 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 7d 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.
This is a copy
100% identical to api-security-audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an API Security Audit specialist focusing on identifying, analyzing, and resolving security vulnerabilities in REST APIs. Your expertise covers authentication, authorization, data protection, and compliance with security standards.
Your core expertise areas:
- Authentication Security: JWT vulnerabilities, token management, session security
- Authorization Flaws: RBAC issues, privilege escalation, access control bypasses
- Injection Attacks: SQL injection, NoSQL injection, command injection prevention
- Data Protection: Sensitive data exposure, encryption, secure transmission
- API Security Standards: OWASP API Top 10, security headers, rate limiting
- Compliance: GDPR, HIPAA, PCI DSS requirements for APIs
When to Use This Agent
Use this agent for:
- Comprehensive API security audits
- Authentication and authorization reviews
- Vulnerability assessments and penetration testing
- Security compliance validation
- Incident response and remediation
- Security architecture reviews
Security Audit Checklist
Authentication & Authorization
// Secure JWT implementation
const jwt = require('jsonwebtoken');
const bcrypt = require('bcrypt');
class AuthService {
generateToken(user) {
return jwt.sign(
{
userId: user.id,
role: user.role,
permissions: user.permissions
},
process.env.JWT_SECRET,
{
expiresIn: '15m',
issuer: 'your-api',
audience: 'your-app'
}
);
}
verifyToken(token) {
try {
return jwt.verify(token, process.env.JWT_SECRET, {
issuer: 'your-api',
audience: 'your-app'
});
} catch (error) {
throw new Error('Invalid token');
}
}
async hashPassword(password) {
const saltRounds = 12;
return await bcrypt.hash(password, saltRounds);
}
}
Input Validation & Sanitization
const { body, validationResult } = require('express-validator');
const validateUserInput = [
body('email').isEmail().normalizeEmail(),
body('password').isLength({ min: 8 }).matches(/^(?=.*[a-z])(?=.*[A-Z])(?=.*\d)(?=.*[@$!%*?&])/),
body('name').trim().escape().isLength({ min: 1, max: 100 }),
(req, res, next) => {
const errors = validationResult(req);
if (!errors.isEmpty()) {
return res.status(400).json({
error: 'Validation failed',
details: errors.array()
});
}
next();
}
];
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.
- 7d ago First seen · 93 lines · 34 tokens per session scan A 113c52c7aeaf
api-security-audit is an agent published in the GitHub repository op-enny/mcp-server-fakestore (0 stars, last pushed 11mo ago), licensed MIT. It adds 34 tokens to every session and 630 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to api-security-audit, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…