security
/security
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.
- Author
- OpenHands ↗
- Repository
- extensions ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Core Security Principles
- Common Security Checks
- Error Handling
SKILL.md preview
--- name: security description: 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. triggers: - security - vulnerability - authentication - authorization - permissions --- 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
Files in this package (5)
- .claude-plugin 1 KB
- .codex-plugin 1 KB
- README.md 1 KB
- SKILL.md 1 KB
- .plugin/plugin.json 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · OpenHands/extensions | 90 | MIT |
| flavien-ia/hypervibe-craft | 100 | Apache-2.0 |
| boshu2/agentops | 100 | Apache-2.0 |
| iamalisson/landspec | 100 | MIT |
| asckye/tia_portal_openness_mcp | 100 | MIT |
| Esposter/Esposter | 100 | Apache-2.0 |
| event4u-app/agent-config | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
Identical content appears in 3 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version d4af756c6f62 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100secure-coding-practices
Secure coding practices and defensive programming patterns for building security-first applications. Use when implementing authentication, handling user input, managing sensitive data, or conducting secure code reviews. - 100security-expert
Expert in application security, vulnerability analysis, secure coding practices, and security auditing. Use for security reviews, threat modeling, authentication/authorization design, and fixing security vulnerabilities. - 90security-review
Diff-scoped security review covering OWASP vulnerabilities, authentication, authorization, and sensitive surfaces. Triggers on security review requests or sensitive changes. - 100common-security-standards
Enforce universal security protocols for safe, resilient software. Use when implementing authentication, encryption, authorization, input validation, secret management, or any security-sensitive feature across any language or framework. - 100securitycards
Apply version-specific secure coding guidance to AI-generated or human-written code that uses supported open source libraries. Use when starting a software project, implementing a security-sensitive feature, or reviewing code for secure defaults, authentication, authorization,… - 100security-architecture-review
Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose…