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 skills add hamzaPixl/pixl-ai --skill api-auditgit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/skills/hamzapixl/pixl-ai/api-audit)<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.
<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>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.00063 | $0.01227 |
| Opus 5 | $0.00032 | $0.00613 |
| Sonnet 5 | $0.00013 | $0.00245 |
| Haiku 4.5 | $0.00006 | $0.00123 |
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.
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
- Framework detection:
package.jsonwith fastify/express/hapi/koa → Node.jspyproject.tomlwith fastapi/django/flask → Pythonapp/api/orpages/api/directory → Next.js API routes
- Route file inventory:
- Fastify: glob for
*.routes.ts,*.controller.ts, files withfastify.get/post/put/delete - Express: files with
router.get/post/put/deleteorapp.get/post/put/delete - FastAPI: files with
@router.get/post/put/deleteor@app.get/post/put/delete - Next.js:
app/api/**/route.tsorpages/api/**/*.ts
- Fastify: glob for
- Auth infrastructure:
- Grep for auth middleware, guards, decorators (
authenticate,requireAuth,Depends,preHandler) - Identify auth strategies (JWT, API key, session, OAuth)
- Grep for auth middleware, guards, decorators (
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:
- Resource naming:
- Nouns, not verbs (
/usersnot/getUsers) - Plural collection names (
/usersnot/user) - Lowercase with hyphens (
/user-profilesnot/userProfiles)
- Nouns, not verbs (
- Method-path alignment:
- GET for reads, POST for creates, PATCH for updates, DELETE for deletes
- No
POST /deleteUserorGET /createItem
- Path parameter naming:
- Consistent ID parameter naming (
:idvs:userIdvs:user_id) - Nested resources use parent path (
/users/:id/postsnot/user-posts/:userId)
- Consistent ID parameter naming (
- Versioning:
- Consistent versioning strategy (path prefix
/v1/or header)
- Consistent versioning strategy (path prefix
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.
- 9d ago First seen · 133 lines · 63 tokens per session scan A 758c13f899ba
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.
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…
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.
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.
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.
api-reviewer
A review of an API contract, the agreed description of how software systems exchange requests, responses, events, or files.
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.