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 kensaurus/cursor-kenji --skill audit-fe-apigit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/audit-fe-api)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/audit-fe-api"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-fe-api/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/kensaurus/cursor-kenji/audit-fe-api"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-fe-api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 84 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 84 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00052 | $0.03324 |
| Opus 5.5 | $0.00021 | $0.01330 |
| Sonnet 5.5 | $0.00010 | $0.00665 |
| Haiku 4.5 | $0.00005 | $0.00332 |
Grade A, and why
audit-fe-api 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 1mo 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 — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend API Audit Skill
Degree of freedom: MIXED — Steps 0, 1, 3–6 [HIGH freedom]; Step 2
Sentry queries and schema SQL [LOW freedom — run exactly].
Read-only. Present findings; the Phase 6 snippets are the fix shape to recommend, not edits to make in this pass.
How to reason
- Observe — quote the FE call site, BE route, and response/error
- Interpret — does the contract match (path, method, params, types)?
- Classify — missing route / mismatch / untyped / cache-gap / correct
- Severity — 404/401/type-mismatch in prod = Critical; cache/prefetch = opportunity
Worked example
Observe:
useUserGETs/api/users/${id}; noapp/api/users/[id]/route.ts; Sentry 25× 404 in 14d. Interpret: FE calls a route the BE never registered. Classify: missing route (Critical). Severity: Critical — guaranteed 404. Finding:hooks/useUser.ts| GET/api/users/:id| Critical | no BE route.
Self-critique before reporting [LOW freedom — do not skip]
- Evidenced — FE file + BE route or Sentry event, not "probably 500"
- Contract, not taste — staleTime advice needs a freshness reason
- Severity justified — Critical = broken contract in prod
- Right owner — live 4xx/5xx repro →
debug-fe-be-integration; DB shape →audit-db-schema - Both sides named — every mismatch lists FE file and BE path (or NOT FOUND)
Step 0: Auto-Detect API Layer
0a. Detect Frontend Stack
| Dependency | Technology |
|---|---|
@tanstack/react-query |
TanStack Query (React Query) |
swr |
SWR |
@reduxjs/toolkit with createApi |
RTK Query |
axios |
Axios HTTP client |
ky |
Ky HTTP client |
ofetch or $fetch |
Nuxt/ofetch |
@trpc/client |
tRPC (type-safe RPC) |
graphql-request or @apollo/client |
GraphQL |
openapi-fetch or openapi-typescript |
OpenAPI typed client |
0b. Detect Backend Stack
Glob: **/app/api/**/route.ts → Next.js App Router API routes
Glob: **/pages/api/**/*.ts → Next.js Pages Router API routes
Glob: **/src/routes/**/*.ts → Express/Hono/Fastify routes
Glob: **/server/api/**/*.ts → Nuxt server routes
Glob: **/src/app.py → Flask/Django
Glob: **/main.go → Go backend
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.
- 1mo ago Changed · +4 lines 9c8de394ed9a
- 1mo ago First seen · 455 lines · 52 tokens per session scan A 89b28be41f85
audit-fe-api is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 26d ago), licensed MIT. It adds 52 tokens to every session and 3,324 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
python-dev
Python backend conventions for this project. Use when implementing or modifying API endpoints, database models/migrations, services, schemas, or backend tests.
developing-genkit-dart
Use when building AI agents in Dart, implementing Genkit flows or tools, integrating LLMs into Dart or Flutter applications, or using Genkit Dart plugins.
create-handler
Create a new API handler following the handler pattern. Use when the user asks to create an endpoint, handler, or route.
generate-api-docs
Generate API documentation from code.
api-docs
Workflow for creating comprehensive API documentation. Use when the user needs to document API endpoints.
opensearch
Workflow for OpenSearch (or Elasticsearch) usage: indexing, search, mappings, and tuning. Use when the user asks about OpenSearch/Elasticsearch.