agentleFS
Sign inStart free
JeremyMorganJeremyMorgan/code-review-skills/skills/api-and-infrastructure/SKILL.md

api-and-infrastructure

Skill15 starsChanged 5 months agoCC0-1.0View on GitHub

Reviews API and infrastructure security configuration, including endpoints, headers, transport, and deployment settings. Use when auditing API or infrastructure hardening.

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If no target path is given above, review the entire codebase.

    line 14
  2. Distinctive:

    Not using wildcard (*) in production

    line 25
  3. Distinctive:

    No stack traces in production

    line 56
  4. Distinctive:

    Prefer minimal, drop-in fix snippets over prose.

    line 78
  5. Distinctive:

    Do not invent files or functions that aren’t present.

    line 80
  6. Distinctive:

    Write this into a markdown file and place it in the audits/ folder.

    line 82

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Target: $ARGUMENTS

If no target path is given above, review the entire codebase.

API & Infrastructure Security

Review API-specific security configurations.

Check for:

  1. CORS configuration
    • Not using wildcard (*) in production
    • Proper origin validation
    • Credentials handling
  2. Rate Limiting
    • Implemented on all endpoints
    • Different limits for different operations
    • Distributed rate limiting for scaled apps
  3. API Versioning security
    • Deprecated version handling
    • Breaking change management
  4. Request size limits
    • Body parser limits
    • File upload restrictions
    • JSON depth limits
  5. HTTP Security Headers
    • Helmet.js configuration
    • CSP headers
    • X-Frame-Options
    • X-Content-Type-Options
    • Strict-Transport-Security
  6. API key/token management
    • Secure storage
    • Rotation policy
    • Scope limitations
  7. Error handling
    • No stack traces in production
    • Generic error messages
    • Proper status codes

Provide:

A structured finding report with the following for each issue:

Title, Severity (Critical/High/Medium/Low), CWE (if applicable), Evidence (file, function, line ranges), and a short Why it matters.

Exploitability notes and, where safe, a minimal PoC or reproduction steps (no real secrets).

Remediation: precise code-level fix or config change (snippets welcome), plus defense-in-depth guidance.

A summary risk score (0–10) and top 3–5 prioritized fixes that reduce risk fastest.

A checklist diff: which items from the “Check for” list are Pass/Fail/Not Applicable.

Constraints & style:

Be concrete and cite exact code locations and identifiers.

Prefer minimal, drop-in fix snippets over prose.

Do not invent files or functions that aren’t present; if context is missing, mark as Unable to verify and say what code would prove it.

Write this into a markdown file and place it in the audits/ folder.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free