mcp-server-fakestore: Agent for Claude Code

.claude/agents/api-security-audit.md

api-security-audit is an agent for Claude Code from op-enny/mcp-server-fakestore. It costs 34 tokens per session (630 once invoked), scanned A, a copy of api-security-audit, MIT.

A coding agent that audits REST APIs, which are web services that exchange data over standard HTTP requests, for security weaknesses.

In plain words
What is it for?
Use it for API security reviews, JWT and authorization checks, injection vulnerability assessments, penetration testing, incident remediation, and GDPR, HIPAA, or PCI DSS validation.
Why use it?
It helps find problems in login, permissions, input handling, data protection, and compliance with API security standards.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is op-enny/mcp-server-fakestore's own configuration. It tells Claude Code how to work on mcp-server-fakestore 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 mcp-server-fakestore configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/op-enny/mcp-server-fakestore/main/.claude/agents/api-security-audit.md
Clone the repo
git clone --depth 1 https://github.com/op-enny/mcp-server-fakestore

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 api-security-audit

README.md
[![agentmods](https://agentmods.dev/badge/agents/op-enny/mcp-server-fakestore/api-security-audit/github.svg)](https://agentmods.dev/agents/op-enny/mcp-server-fakestore/api-security-audit)
Your own site
<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.

agentmods 80×15 button for api-security-audit

Your own site · 80×15
<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>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 630 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 100% copy Near-identical to another mod 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.00034 $0.00630
Opus 5 $0.00017 $0.00315
Sonnet 5 $0.00007 $0.00126
Haiku 4.5 $0.00003 $0.00063

Measured 7d ago against content hash 113c52c7aeaf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

Origin

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.

.claude/agents/api-security-audit.md · 93 lines

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();
  }
];

Read the full file on GitHub · 93 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. 7d ago First seen · 93 lines · 34 tokens per session scan A 113c52c7aeaf

Subscribe to this mod's changes

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.

Related

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.

github/awesome-copilot · 31 tokens

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.

davepoon/buildwithclaude · 51 tokens

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.

jeremylongshore/tons-of-skills-marketplace · 36 tokens

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…

avelikiy/great_cto · 106 tokens

gate

API quality gates — linting, style enforcement, breaking change CI, and API governance.

tonone-ai/tonone · 19 tokens

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…

StefanTheCode/dotnet-ai-toolkit · 102 tokens