Skip to content
TrustedSkillsbeta
Back to all skills

Security Guardian

Checked
caomeiyouren·vlatest·security·MIT

Proactively identifies and mitigates potential security threats using real-time analysis and automated response actions.

Repository

Install on your platform

This skill no longer installs under the name security-guardian. SKILL.md is marked internal, so the skills CLI hides it.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-21. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

caomeiyouren

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 caomeiyouren/momei at 02346816ce.

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

Commit
02346816ce
Manifest
.github/skills/security-guardian/SKILL.md
Scanned
1 file, 35 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

The Security Guardian skill proactively identifies and mitigates potential security threats through real-time analysis and automated response actions. It focuses on detecting vulnerabilities like hardcoded secrets (API keys, tokens, passwords), SQL injection and XSS risks, authorization bypasses, and insecure dependencies within package.json files. This skill is designed to help ensure the security of server-side code and APIs.

When to use it

  • When making changes to servers or APIs, particularly when modifying server/utils/permission.ts.
  • Before deploying applications with sensitive data handling capabilities.
  • During audits of login logic or other critical operations.
  • For reviewing code that involves deletion or updates of sensitive data.
  • To proactively identify and address potential security vulnerabilities in dependencies.

Key capabilities

  • Secrets Scanning: Detects hardcoded API keys, tokens, and passwords.
  • Injection Detection: Identifies SQL injection and XSS risks.
  • Authorization Check: Verifies proper session and role validation for APIs.
  • Dependency Audit: Checks package.json files for insecure packages.
  • Double Auditing: Requires a second review for deletion or sensitive data update operations.

Example prompts

  • "Review this login logic." (The skill will check for secure hashing, rate limiting, and password logging.)
  • "Scan the codebase for hardcoded API keys."
  • "Audit package.json for vulnerable dependencies."

Tips & gotchas

  • For server/API changes, it's mandatory to check calls within server/utils/permission.ts.
  • If the skill is uncertain about a code segment’s security, it will report this so that a human can manually verify.
  • This skill focuses on identifying potential vulnerabilities; manual verification and remediation are often required.