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/ckaraca/fake-store-mcp/api-security-auditgit clone --depth 1 https://github.com/ckaraca/fake-store-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/ckaraca/fake-store-mcp/api-security-audit)<a href="https://agentmods.dev/agents/ckaraca/fake-store-mcp/api-security-audit"><img src="https://agentmods.dev/badge/agents/ckaraca/fake-store-mcp/api-security-audit.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 | $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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- api-security-audit — 100% identical, 0 lines differ
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.
- 3d ago First seen · 93 lines · 34 tokens per session scan A 113c52c7aeaf
api-security-audit is an agent published in the GitHub repository ckaraca/fake-store-mcp (0 stars, last pushed 6mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
weather-assistant
Primary weather agent that answers any weather, air quality, or timezone question using all 8 MCP weather server tools. Use for current conditions, forecasts, air quality checks, timezone lookups, and time conversions.
work-verifier
Validates completed work. Use after tasks are marked done to confirm implementations are functional.
documcp-memory
Work with DocuMCP's Knowledge Graph memory system.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.
B-phase-2-cache
You build the three-tier cache (LRU + disk CBOR + delta encoding) on top of Agent A's registry.
A-phase-0-1-and-x3
You are the lead agent for the MCP Conductor v3 sprint. You unblock every other agent. Land Phase 1 cleanly or the whole sprint stalls.