Skip to content
TrustedSkillsbeta
Back to all skills

Reverse Proxy

Checked
bagelhole·vlatest·cloud·MIT

This Reverse Proxy skill masks your server’s IP, enhancing security and enabling features like load balancing for improved performance and resilience.

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 bagelhole/devops-security-agent-skills --skill reverse-proxy -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

bagelhole

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 bagelhole/devops-security-agent-skills at 0365f57a07.

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

Scanned
1 file, 385 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 allows an AI agent to configure and manage a reverse proxy. It can route incoming requests to different backend servers, improving security and load balancing across your infrastructure. The skill provides the ability to define rules for request routing based on various criteria like hostnames or URL paths.

When to use it

  • Load Balancing: Distribute traffic evenly across multiple application servers to prevent overload and improve performance.
  • Security Enhancement: Hide internal server details from external clients, adding a layer of protection against direct attacks.
  • SSL Termination: Offload SSL encryption/decryption from backend servers, freeing up their resources.
  • Centralized Access: Provide a single point of access to multiple applications running on different ports or servers.

Key capabilities

  • Request routing based on hostname and URL path
  • SSL termination configuration
  • Backend server management
  • Load balancing across multiple backend servers

Example prompts

  • "Configure a reverse proxy to route requests for api.example.com to 192.168.1.10:8080."
  • "Set up SSL termination on port 443 and forward traffic to internal-app:3000."
  • “Create a rule that routes all requests under /admin to the server at 10.0.0.5:9000.”

Tips & gotchas

The skill requires knowledge of network configurations and basic understanding of reverse proxy concepts. Incorrect configuration can lead to service unavailability, so careful testing is recommended after deployment.