A command for auditing an API implementation for security problems. It checks areas such as authentication, permissions, input handling, data exposure, rate limits, and common OWASP Top 10 risks.

Use it to review API code and specifications, rate findings by severity, provide proof-of-concept examples, and suggest practical fixes.

It helps reveal weaknesses that may let attackers access restricted data, inject commands, overwhelm the service, or learn sensitive information.

audit — Command for Claude Code by mrlm-xyz/demo-claude-marketplace

Install

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.

Clone the repo

git clone --depth 1 https://github.com/mrlm-xyz/demo-claude-marketplace

Made for: Claude Code.

Or install api-guardian, the plugin that ships this one along with the rest of its 2 skills, 2 commands, 2 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/mrlm-xyz/demo-claude-marketplace/audit/github.svg)](https://agentmods.dev/commands/mrlm-xyz/demo-claude-marketplace/audit)

Your own site

<a href="https://agentmods.dev/commands/mrlm-xyz/demo-claude-marketplace/audit"><img src="https://agentmods.dev/badge/commands/mrlm-xyz/demo-claude-marketplace/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/mrlm-xyz/demo-claude-marketplace/audit"><img src="https://agentmods.dev/badge/commands/mrlm-xyz/demo-claude-marketplace/audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 278 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 original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00020	$0.00278
Opus 5.5	$0.00008	$0.00111
Sonnet 5.5	$0.00004	$0.00056
Haiku 4.5	$0.00002	$0.00028

Measured 2mo ago against content hash a5dfcc40cda5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

claude-plugins/api-guardian/commands/audit.md · 44 lines

What it actually says

Audit Command

Conduct a thorough security audit of API implementation to identify vulnerabilities and recommend mitigations.

Scope

This command performs security analysis covering:

Authentication mechanisms (OAuth, JWT, API keys)
Authorization and access control logic
Input validation and sanitization
Injection vulnerabilities (SQL, NoSQL, command)
Sensitive data exposure and leakage
Rate limiting and DoS protection
Security headers and CORS configuration
Dependency vulnerabilities

Execution Flow

Review API specification and implementation
Analyze authentication and session management
Check authorization logic and access controls
Test input validation and sanitization
Scan for injection vulnerabilities
Review error handling and information disclosure
Check rate limiting and quota enforcement
Verify encryption for sensitive data
Document findings with severity levels
Recommend specific mitigations with examples

Constraints

Use api-guardian security skills for analysis
Follow OWASP Top 10 methodology
Provide severity ratings (Critical, High, Medium, Low)
Include proof of concept for findings
Recommend practical mitigations
Consider both design and implementation issues
Document assumptions and scope limitations
Prioritize findings by risk and impact

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.

2mo ago First seen · 44 lines · 20 tokens per session scan A a5dfcc40cda5

Subscribe to this mod's changes

audit is a command published in the GitHub repository mrlm-xyz/demo-claude-marketplace (35 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 278 once invoked, about $0.0001 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.