Skip to content
TrustedSkillsbeta
Back to all skills

Graphql Security

Checked
pluginagentmarketplace·vlatest·backend

Helps with GraphQL, security as part of developing backend services and APIs 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 pluginagentmarketplace/custom-plugin-graphql --skill graphql-security -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

pluginagentmarketplace

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

    Makes no network calls.

    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.

  • 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 pluginagentmarketplace/custom-plugin-graphql at ca6262e7a5.

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

Commit
ca6262e7a5
Manifest
skills/graphql-security/SKILL.md
Scanned
6 files, 693 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 GraphQL security features. It helps protect GraphQL APIs from common vulnerabilities and attacks. Specifically, it offers protection against denial of service (DoS) attacks and query complexity exploits.

When to use it

  • Protecting a public GraphQL API: Ensure your API is resilient to malicious queries that could overload the server.
  • Enforcing query limits: Prevent users from submitting excessively complex or resource-intensive queries.
  • Securing internal APIs: Safeguard backend services exposed via GraphQL endpoints.
  • Auditing potential vulnerabilities: Identify and mitigate security risks within your GraphQL implementation.

Key capabilities

  • Denial of Service (DoS) protection
  • Query complexity limiting
  • Vulnerability mitigation

Example prompts

  • "Implement a query depth limit of 10."
  • "Protect against denial-of-service attacks on the /graphql endpoint."
  • "What is the current query complexity threshold?"

Tips & gotchas

This skill requires access to and configuration within your GraphQL server environment. Incorrectly configured limits may impact legitimate users, so careful testing is recommended.