Skip to content
TrustedSkillsbeta
Back to all skills

Api Hardening

Checked
jamditis·vlatest·backend·MIT

Provides API guidance and assistance for agent workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jamditis/claude-skills-journalism --skill api-hardening -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jamditis

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: 127.0.0.1.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    127.0.0.1local

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jamditis/claude-skills-journalism at 8a047d85f3.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
8a047d85f3
Manifest
security-toolkit/skills/api-hardening/SKILL.md
Scanned
2 files, 1,121 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides guidance and code examples for API hardening, focusing on defense-in-depth strategies to protect APIs from abuse, injection attacks, and data leakage. It specifically demonstrates rate limiting implementation using Express.js and Redis, offering different configurations for general API usage, authentication endpoints, and password reset requests. The goal is to prevent brute force attacks, accidental or intentional DDoS events, and unexpected cloud provider costs.

When to use it

  • When building APIs that require protection against abuse and malicious attacks.
  • During the development of authentication flows where limiting login attempts is crucial.
  • To implement rate limits for password reset functionality to prevent misuse.
  • When needing guidance on securing Express.js applications with rate limiting.

Key capabilities

  • Provides code examples for implementing API rate limiting in Express.js.
  • Demonstrates the use of express-rate-limit and Redis for storing rate limit data.
  • Offers different rate limiting configurations based on endpoint sensitivity (general, authentication, password reset).
  • Includes example logic to skip rate limiting for health check endpoints.
  • Shows how to customize rate limits by combining IP address and email in the key generator for authentication.

Example prompts

  • "Show me an example of implementing a general API rate limit using Express.js."
  • "How can I rate limit login attempts with Express.js, considering both IP address and email?"
  • "Give me code to set up a password reset rate limiter in my Express.js application."

Tips & gotchas

  • Requires an active Redis server accessible via the REDIS_URL environment variable.
  • The provided examples are specific to Express.js; adaptation may be needed for other frameworks.
  • Consider carefully choosing appropriate rate limit values (max) based on your application's needs and expected traffic.