security-patterns

Enforce secure development guardrails for Kailash SDK implementations.

Updated Oct 10, 2025
One-click install
npx skills add https://github.com/FFOO6866/lead2cash --skill security-patterns-ffoo6866
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-patterns
Source: https://github.com/FFOO6866/lead2cash/tree/main/.claude/skills/18-security-patterns
Command: npx skills add https://github.com/FFOO6866/lead2cash --skill security-patterns-ffoo6866

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides mandatory, production-ready security patterns that help teams avoid common vulnerabilities such as secret leakage, injection attacks, weak authn/authz handling, SSRF, and insecure error logging.

Core Features & Use Cases

  • Secret-safe development: enforces a “never hardcode secrets” workflow using environment variables or secure vaults.
  • Injection and validation guardrails: requires validation of all user inputs and use of parameterized query pathways to prevent SQL/code injection.
  • Safe outbound HTTP handling: mitigates SSRF by validating URL schemes, blocking dangerous IP ranges, resisting DNS rebinding, and pinning resolved IPs.
  • Authn/Authz and OWASP alignment: supports secure API design practices grounded in OWASP Top 10 prevention.
  • Audit-chain cryptographic robustness: mandates canonical-form helpers for byte-stable anchor hashing, constant-time hash comparisons, and ensuring verify paths are exercised in hot paths.
  • Log and error hygiene: prevents sensitive data from being logged and returns generic errors to avoid leaking internal details.

Quick Start

Use the security-patterns skill when you are implementing or reviewing SDK code that accepts external input, manages credentials, performs outbound API calls, or defines authn/authz logic.

Frequently Asked Questions about security-patterns

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

FAQPage Schema
How do I prevent secret leakage when implementing SDK adapters?

Prevent secret leakage by enforcing a strict "never hardcode secrets" workflow using environment variables or secure vaults, and by suppressing sensitive logs to avoid exposing credentials during SDK adapter implementation.

What's the best way to prevent SSRF in outbound HTTP calls?

Mitigate SSRF by validating URL schemes, blocking dangerous IP ranges, resisting DNS rebinding attacks, and pinning resolved IPs to ensure outbound HTTP calls only reach validated, safe network targets.

How do I implement input validation and injection prevention for query paths?

Implement input validation and injection prevention by requiring validation of all user inputs and mandating parameterized query pathways to block SQL and code injection in DataFlow query paths.

How does audit-chain cryptographic robustness work for anchor hashing?

Audit-chain robustness mandates canonical-form helpers for byte-stable anchor hashing, requires constant-time comparisons on hash equality, and ensures verify paths are actively exercised in production hot paths.

Does this approach align with OWASP Top 10 prevention for API design?

Yes, the secure API design practices are grounded in OWASP Top 10 prevention, specifically supporting safe authentication and authorization logic wiring while returning generic errors to avoid leaking internal details.

Why do I need constant-time comparisons for hash equality in production hot paths?

Constant-time comparisons on hash equality are required to prevent timing side-channel attacks, ensuring attackers cannot deduce canonical byte-stable hashes or audit-chain verification states by measuring response times.