sharp-edges

Identify security design flaws and footguns in codebases and libraries.

31|4|Updated Apr 6, 2026

Search Tags:#security #configuration #cryptography #risk-assessment #code-review #api-design #footguns

Ready to run

npx skills add https://github.com/kissrosecicd-hub/agents-evolution --skill sharp-edges-kissrosecicd-hub

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sharp-edges
Source: https://github.com/kissrosecicd-hub/agents-evolution/tree/main/.agents/skills/tob-sharp-edges
Command: npx skills add https://github.com/kissrosecicd-hub/agents-evolution --skill sharp-edges-kissrosecicd-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security teams struggle to identify subtle design decisions that introduce risk, such as unsafe defaults, misconfigurations, and API surface footguns. This Skill provides a structured framework to surface these issues during reviews.

Core Features & Use Cases

Detects common security design flaws across authentication, authorization, cryptography, and configuration patterns.
Guides security reviews with concrete detection patterns, mitigations, and a workflow for risk prioritization.
Use during API/library reviews, config audits, and security design sessions to produce actionable remediation notes.

Quick Start

Provide a codebase or library to review and I will return a prioritized list of security footguns with mitigations.

Frequently Asked Questions about sharp-edges

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify security design footguns in my codebase?▼

Identify security design footguns by applying a structured framework of detection patterns for algorithm choices, unsafe defaults, and misconfigurations. This surfaces usability-induced risks during code reviews and outputs a prioritized risk report with actionable mitigations.

What are security design footguns and why do they matter?▼

Security design footguns are subtle API design decisions, unsafe defaults, and misconfigurations that introduce risk into codebases. They matter because they create usability-induced vulnerabilities across authentication, authorization, and cryptography patterns that are often missed without structured detection.

Can I use this to audit cryptographic API designs and configurations?▼

Yes, you can audit cryptographic API designs and configurations using structured detection patterns for algorithm choices and error handling. It assesses unsafe defaults and misconfigurations to produce a prioritized risk report with concrete mitigations.

What's the best way to review APIs for unsafe defaults and misconfigurations?▼

The best way to review APIs for unsafe defaults is using a structured set of detection patterns targeting type-safety, error handling, and configuration audits. This approach systematically surfaces misconfigurations and usability-induced risks, generating a prioritized risk report for remediation.

When do I need a structured risk assessment for library and API reviews?▼

You need a structured risk assessment for library and API reviews when security teams must surface subtle design flaws like unsafe defaults, misconfigurations, and cryptographic API footguns. This provides concrete detection patterns and a workflow for risk prioritization to guide remediation.