hims-security-companion

Review code and architecture for OWASP Top 10 and healthcare-specific security vulnerabilities.

Updated Jan 3, 2026
One-click install
npx skills add https://github.com/CJCreator-New/care-harmony-hub --skill hims-security-companion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hims-security-companion
Source: https://github.com/CJCreator-New/care-harmony-hub/tree/main/.agents/skills/hims-security-companion
Command: npx skills add https://github.com/CJCreator-New/care-harmony-hub --skill hims-security-companion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses critical security vulnerabilities in healthcare systems, focusing on risks that could lead to Protected Health Information (PHI) breaches or clinical harm.

Core Features & Use Cases

  • Vulnerability Assessment: Reviews code and architecture against OWASP Top 10 and healthcare-specific threats like IDOR, broken authentication, and injection.
  • Security Best Practices: Recommends security headers, rate limiting, SAST/DAST integration, and secure coding practices.
  • Use Case: A developer submits new API endpoints for patient record access. This Skill analyzes the code to ensure proper authorization checks are in place and flags any potential for insecure direct object references.

Quick Start

Review the provided code snippet for potential security vulnerabilities related to patient data access.

Frequently Asked Questions about hims-security-companion

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

FAQPage Schema
How do I check my healthcare API code for PHI breach vulnerabilities?

To check for PHI breach vulnerabilities, review your code against OWASP Top 10 and healthcare-specific threats like IDOR, broken authentication, and injection, prioritizing risks leading to clinical harm as Critical.

What is the best way to prevent insecure direct object reference in patient record access endpoints?

Preventing insecure direct object reference requires analyzing your patient record access endpoints to ensure proper authorization checks are in place, flagging any potential unauthorized access to sensitive data.

How does code review for sensitive data exposure identify injection risks?

Code review for sensitive data exposure identifies injection risks by analyzing code and architecture, providing recommendations for parameterized queries and secure coding practices to mitigate unauthorized data access.

Can I integrate SAST and DAST tools to secure healthcare applications?

Yes, you can integrate SAST and DAST tools to secure healthcare applications, as vulnerability assessments provide recommendations for SAST/DAST integration alongside security headers and rate limiting.

What security headers and rate limiting configurations do I need for healthcare compliance?

For healthcare compliance, you need security headers and rate limiting configurations recommended during vulnerability assessments that review code architecture against OWASP Top 10 and healthcare-specific threats.

When should I prioritize broken authentication vulnerabilities in a healthcare system security review?

You should prioritize broken authentication vulnerabilities in a healthcare security review when assessing risks that could lead to Protected Health Information breaches or clinical harm, classifying them as Critical.