Skip to content
TrustedSkillsbeta
Back to all skills

Frontend Security

Checked
schalkneethling·vlatest·security·MIT

Helps with frontend development, security as part of implementing security and authentication 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 schalkneethling/webdev-agent-skills --skill frontend-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

schalkneethling

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 schalkneethling/webdev-agent-skills at 85710096f4.

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

Commit
85710096f4
Manifest
frontend-security/SKILL.md
Scanned
10 files, 2,097 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 performs security audits of frontend codebases to identify vulnerabilities and potential weaknesses. It scans for dangerous coding patterns, reviews framework-specific risks, validates existing defensive measures (like CSP and CSRF tokens), and checks project dependencies for known vulnerabilities. The skill then categorizes findings by severity and provides remediation guidance based on the identified issues.

When to use it

  • When starting a new frontend project to proactively identify security concerns early on.
  • During code reviews to ensure secure coding practices are followed.
  • After making significant changes to a frontend codebase to assess potential security impacts.
  • As part of a regular security assessment process for existing applications.
  • To investigate specific security concerns or reports within a frontend project.

Key capabilities

  • Vulnerability Scanning: Searches codebases for indicators of common vulnerabilities like Cross-Site Scripting (XSS), CSRF, and sensitive data exposure.
  • Framework Risk Review: Checks for framework-specific security bypass patterns.
  • Defensive Measure Validation: Verifies the presence and correctness of security controls such as Content Security Policy (CSP) and CSRF tokens.
  • Dependency Checking: Reviews npm/node dependencies for known vulnerabilities.
  • Reporting & Guidance: Categorizes findings by severity and provides links to relevant documentation for remediation.

Example prompts

  • "Perform a frontend security audit of this codebase."
  • "Check this project for XSS vulnerabilities."
  • "Review the forms in this application for CSRF protection."
  • "Audit dependencies for known vulnerabilities."

Tips & gotchas

  • The skill relies on pattern matching (grep) and may produce false positives. Careful review of findings is necessary.
  • The accuracy of the audit depends on the completeness and quality of the codebase being analyzed.
  • Refer to the provided reference documentation for detailed guidance on addressing identified issues.