api-audit

api-audit is a skill for Claude Code from hamzaPixl/pixl-ai. It costs 63 tokens per session (1,227 once invoked), scanned A, original, MIT.

A read-only checklist and process for reviewing web API endpoints. An API is the interface that lets software exchange requests and responses, and this review checks its routes, data formats, validation, authentication, and REST conventions.

In plain words
What is it for?
Use it to audit Fastify, Express, FastAPI, or Next.js API routes for naming consistency, response shapes, validation, authentication, and REST design.
Why use it?
It helps reveal inconsistent endpoint names or responses, missing input checks, and authorization gaps. It also organizes findings into a prioritized report.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the pixl-crew plugin — 93 skills, 14 agents, 6 hooks shipped together

Good fit Use it to audit Fastify, Express, FastAPI, or Next.js API routes for naming consistency, response shapes, validation, authentication, and REST design.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hamzapixl/pixl-ai/api-audit
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.

Any agent
npx skills add hamzaPixl/pixl-ai --skill api-audit
Clone the repo
git clone --depth 1 https://github.com/hamzaPixl/pixl-ai

Made for: Claude Code.

Or install pixl-crew, the plugin that ships this one along with the rest of its 93 skills, 14 agents, 6 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/api-audit/github.svg)](https://agentmods.dev/skills/hamzapixl/pixl-ai/api-audit)
Your own site
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/api-audit"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/api-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-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/api-audit"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/api-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,227 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.01227
Opus 5 $0.00032 $0.00613
Sonnet 5 $0.00013 $0.00245
Haiku 4.5 $0.00006 $0.00123

Measured 9d ago against content hash 758c13f899ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

api-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 9d 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.

packages/crew/skills/api-audit/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

API audit pipeline: discovery → endpoint inventory → naming audit → response audit → validation audit → auth audit → scorecard. Read-only analysis that produces a prioritized report.

Required References

Before starting, read references/backend/api-design.md for REST conventions, naming rules, and response format standards.

Step 1: Discovery

  1. Framework detection:
    • package.json with fastify/express/hapi/koa → Node.js
    • pyproject.toml with fastapi/django/flask → Python
    • app/api/ or pages/api/ directory → Next.js API routes
  2. Route file inventory:
    • Fastify: glob for *.routes.ts, *.controller.ts, files with fastify.get/post/put/delete
    • Express: files with router.get/post/put/delete or app.get/post/put/delete
    • FastAPI: files with @router.get/post/put/delete or @app.get/post/put/delete
    • Next.js: app/api/**/route.ts or pages/api/**/*.ts
  3. Auth infrastructure:
    • Grep for auth middleware, guards, decorators (authenticate, requireAuth, Depends, preHandler)
    • Identify auth strategies (JWT, API key, session, OAuth)

Step 2: Endpoint Inventory

For each endpoint, extract:

Field Source
Method GET/POST/PATCH/PUT/DELETE
Path Route path with parameters
Handler Function name and file location
Auth Required/optional/none
Validation Input schema (Zod/Joi/Pydantic) or none
Response type Typed response or untyped

Build complete inventory table.

Step 3: Naming Audit

Check each endpoint against REST conventions:

  1. Resource naming:
    • Nouns, not verbs (/users not /getUsers)
    • Plural collection names (/users not /user)
    • Lowercase with hyphens (/user-profiles not /userProfiles)
  2. Method-path alignment:
    • GET for reads, POST for creates, PATCH for updates, DELETE for deletes
    • No POST /deleteUser or GET /createItem
  3. Path parameter naming:
    • Consistent ID parameter naming (:id vs :userId vs :user_id)
    • Nested resources use parent path (/users/:id/posts not /user-posts/:userId)
  4. Versioning:
    • Consistent versioning strategy (path prefix /v1/ or header)

Read the full file on GitHub · 133 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. 9d ago First seen · 133 lines · 63 tokens per session scan A 758c13f899ba

Subscribe to this mod's changes

api-audit is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 1,227 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

platform-apex-generate

Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…

forcedotcom/sf-skills · 122 tokens

flow-next-impl-review

Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.

gmickel/flow-next · 34 tokens

flow-next-resolve-pr

Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.

gmickel/flow-next · 36 tokens

api-contract-review

Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.

TencentCloudBase/CloudBase-AI-Toolkit · 54 tokens

api-reviewer

A review of an API contract, the agreed description of how software systems exchange requests, responses, events, or files.

TestAny-io/testany-agent-skills · 64 tokens

principle-model-the-domain

Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.

cursor/plugins · 39 tokens