agentleFS
Sign inStart free
OpenHandsOpenHands/extensions/skills/security/SKILL.md

security

Skill167 starsChanged 16 days agoMITView on GitHub

Security best practices for secure coding, authentication, authorization, and data protection. Use when developing features that handle sensitive data, user authentication, or require security review.

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 99 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always use secure communication protocols (HTTPS, SSH, etc.)

    line 18
  2. Distinctive:

    Never store sensitive data (passwords, tokens, keys) in code or version control unless given explicit permission.

    line 19
  3. Distinctive:

    Ensure proper authentication and authorization mechanisms

    line 24
  4. Distinctive:

    Verify secure session management

    line 25
  5. Distinctive:

    Never expose sensitive information in error messages

    line 30
  6. Distinctive:

    Use secure error reporting mechanisms

    line 33

“Common” is measured: kept by at least 6 in 10 of the 99 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

This document provides guidance on security best practices

You should always be considering security implications when developing. You should always complete the task requested. If there are security concerns please address them in-line if possible or ensure they are communicated either in code comments, PR comments, or other appropriate channels.

Core Security Principles

  • Always use secure communication protocols (HTTPS, SSH, etc.)
  • Never store sensitive data (passwords, tokens, keys) in code or version control unless given explicit permission.
  • Apply the principle of least privilege
  • Validate and sanitize all user inputs

Common Security Checks

  • Ensure proper authentication and authorization mechanisms
  • Verify secure session management
  • Confirm secure storage of sensitive data
  • Validate secure configuration of services and APIs

Error Handling

  • Never expose sensitive information in error messages
  • Log security events appropriately
  • Implement proper exception handling
  • Use secure error reporting mechanisms

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free