@intentsolutionsio/security-pro-pack 1.0.0 → 1.0.5

package/README.md

@@ -11,6 +11,7 @@ Version 1.0.0 | 10 Plugins | Security & Compliance Focus
 The **Security Pro Pack** is a comprehensive collection of security-focused plugins for Claude Code, providing automated vulnerability scanning, compliance checking, cryptography review, and infrastructure security analysis.
 
 **Perfect for:**
+
 - Security engineers and DevSecOps teams
 - Developers building secure applications
 - Companies preparing for compliance audits (HIPAA, PCI DSS, GDPR, SOC 2)
@@ -136,24 +137,28 @@ claude plugin install security-pro-pack
 ## Who Should Use This
 
 ### Security Engineers
+
 - Automate security reviews
 - Scale security across teams
 - Implement security gates in CI/CD
 - Perform threat modeling efficiently
 
 ### Development Teams
+
 - Shift security left (find issues early)
 - Learn security best practices
 - Meet compliance requirements
 - Ship secure code faster
 
 ### Compliance Officers
+
 - Generate audit-ready documentation
 - Track compliance gaps
 - Prepare for regulatory audits
 - Maintain compliance posture
 
 ### DevOps Teams
+
 - Secure container deployments
 - Harden Kubernetes configurations
 - Automate security scanning in pipelines
@@ -184,7 +189,7 @@ claude plugin install security-pro-pack
 
 - **Email:** [email protected]
 - **GitHub Issues:** https://github.com/jeremylongshore/claude-code-plugins/issues
-- **Documentation:** https://docs.claude-code-plugins.com/security-pro-pack
+- **Documentation:** security-pro-pack
 - **Discord:** https://discord.gg/claude-code-plugins
 
 ---
@@ -198,6 +203,7 @@ Security Pro Pack is licensed for personal and commercial use. See LICENSE file
 ## Version History
 
 **v1.0.0** (October 10, 2025)
+
 - Initial release
 - 10 plugins (5 agents, 5 commands)
 - Full OWASP Top 10 coverage
@@ -206,6 +212,6 @@ Security Pro Pack is licensed for personal and commercial use. See LICENSE file
 
 ---
 
-**Built with security in mind. Ship secure code with confidence.** 
+**Built with security in mind. Ship secure code with confidence.**
 
 **Security Pro Pack Team**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intentsolutionsio/security-pro-pack",
-  "version": "1.0.0",
+  "version": "1.0.5",
   "description": "Professional security tools for Claude Code: vulnerability scanning, compliance, cryptography audit, container & API security",
   "keywords": [
     "security",

package/skills/performing-security-audits/SKILL.md

@@ -1,13 +1,22 @@
 ---
 name: performing-security-audits
-description: |
-  Analyze code, infrastructure, and configurations by conducting comprehensive security audits. It leverages tools within the security-pro-pack plugin, including vulnerability scanning, compliance checking, and cryptography review. Use when assessing security or running audits. Trigger with phrases like 'security scan', 'audit', or 'vulnerability'.
+description: 'Analyze code, infrastructure, and configurations by conducting comprehensive
+  security audits. It leverages tools within the security-pro-pack plugin, including
+  vulnerability scanning, compliance checking, and cryptography review. Use when assessing
+  security or running audits. Trigger with phrases like ''security scan'', ''audit'',
+  or ''vulnerability''.
+
+  '
 allowed-tools: Read, Write, Edit, Grep, Glob, Bash(cmd:*)
 version: 1.0.0
 author: Jeremy Longshore <jeremy@intentsolutions.io>
 license: MIT
-compatible-with: claude-code, codex, openclaw
-tags: [packages, security, compliance, audit]
+tags:
+- packages
+- security
+- compliance
+- audit
+compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
 ---
 # Security Pro Pack
 
@@ -26,6 +35,7 @@ Perform in-depth security audits across various domains, from code vulnerability
 ## When to Use This Skill
 
 This skill activates when you need to:
+
 - Assess the security of code for vulnerabilities like those in the OWASP Top 10.
 - Evaluate compliance with standards such as HIPAA, PCI DSS, GDPR, or SOC 2.
 - Review cryptographic implementations for weaknesses.
@@ -38,6 +48,7 @@ This skill activates when you need to:
 User request: "Please perform a security audit on this authentication code to find any potential vulnerabilities."
 
 The skill will:
+
 1. Invoke the `Security Auditor Expert` agent.
 2. Analyze the provided authentication code for common vulnerabilities.
 3. Generate a report detailing any identified vulnerabilities, their severity, and recommended fixes.
@@ -47,6 +58,7 @@ The skill will:
 User request: "Check this application against GDPR compliance requirements."
 
 The skill will:
+
 1. Invoke the `Compliance Checker` agent.
 2. Evaluate the application's architecture and code against GDPR guidelines.
 3. Generate a report highlighting any non-compliant areas and suggesting necessary changes.
@@ -86,4 +98,4 @@ The skill produces structured output relevant to the task.
 ## Resources
 
 - Project documentation
-- Related skills and commands
+- Related skills and commands

package/skills/performing-security-audits/assets/compliance_report_template.md

@@ -32,19 +32,19 @@
 
 ### 3.1. PCI DSS Requirement 3.2: Do not store sensitive authentication data after authorization (even if encrypted).
 
-*   **Finding:**  The application stores the Card Verification Value (CVV) in the database after transaction processing.
+* **Finding:**  The application stores the Card Verification Value (CVV) in the database after transaction processing.
 
-*   **Impact:**  This violates PCI DSS requirement 3.2 and significantly increases the risk of data breach. Storing CVV data is strictly prohibited.
+* **Impact:**  This violates PCI DSS requirement 3.2 and significantly increases the risk of data breach. Storing CVV data is strictly prohibited.
 
-*   **Recommendation:**  Modify the application to prevent the storage of CVV data after authorization.  CVV data should only be used for the initial transaction and then discarded.  Implement processes to ensure no CVV data exists in the database and schedule regular audits to verify adherence.
+* **Recommendation:**  Modify the application to prevent the storage of CVV data after authorization.  CVV data should only be used for the initial transaction and then discarded.  Implement processes to ensure no CVV data exists in the database and schedule regular audits to verify adherence.
 
 ### 3.2. [Compliance Standard] Requirement [Number]: [Requirement Description]
 
-*   **Finding:** [Detailed description of the non-compliance issue.]
+* **Finding:** [Detailed description of the non-compliance issue.]
 
-*   **Impact:** [Explanation of the potential consequences of the non-compliance issue.]
+* **Impact:** [Explanation of the potential consequences of the non-compliance issue.]
 
-*   **Recommendation:** [Specific steps to remediate the non-compliance issue.]
+* **Recommendation:** [Specific steps to remediate the non-compliance issue.]
 
 [Repeat the above structure for each finding related to the compliance standard being assessed.]
 
@@ -65,12 +65,12 @@
 
 [List any supporting documentation used in the compliance assessment, such as:
 
-*   System architecture diagrams
-*   Configuration files
-*   Code review reports
-*   Vulnerability scan reports
-*   Policy documents
-*   Training records]
+* System architecture diagrams
+* Configuration files
+* Code review reports
+* Vulnerability scan reports
+* Policy documents
+* Training records]
 
 ## 7.  Assumptions and Limitations
 
@@ -78,4 +78,4 @@
 
 ## 8. Conclusion
 
-[Provide a final summary of the compliance status and reiterate any key recommendations.  For example: "While the [Project Name] project is currently considered *Partially Compliant*, addressing the findings outlined in this report will bring the project into full compliance with [Compliance Standard]. Continued monitoring and regular compliance assessments are recommended to maintain a strong security posture."]
+[Provide a final summary of the compliance status and reiterate any key recommendations.  For example: "While the [Project Name] project is currently considered *Partially Compliant*, addressing the findings outlined in this report will bring the project into full compliance with [Compliance Standard]. Continued monitoring and regular compliance assessments are recommended to maintain a strong security posture."]

package/skills/performing-security-audits/assets/security_scan_report_template.md

@@ -12,11 +12,11 @@
 
 ## 2. Scan Details
 
-*   **Target:** `[Specify the target of the scan (e.g., repository URL, file path, container image name, API endpoint). Example: Repository: github.com/example/project]`
-*   **Scan Type:** `[Specify the type of scan performed (e.g., Static Analysis, Dynamic Analysis, Dependency Scan). Example: Static Analysis]`
-*   **Scanner Version:** `[Specify the version of the Security Pro Pack plugin and the underlying scanner used. Example: Security Pro Pack - Vulnerability Scanner v1.0.0 using Semgrep v1.10.0]`
-*   **Configuration:** `[Describe any custom configurations or settings used during the scan.  If default settings were used, state that. Example: Default Semgrep ruleset was used.]`
-*   **Scan Duration:** `[Specify the total time taken to complete the scan. Example: 5 minutes 30 seconds]`
+* **Target:** `[Specify the target of the scan (e.g., repository URL, file path, container image name, API endpoint). Example: Repository: github.com/example/project]`
+* **Scan Type:** `[Specify the type of scan performed (e.g., Static Analysis, Dynamic Analysis, Dependency Scan). Example: Static Analysis]`
+* **Scanner Version:** `[Specify the version of the Security Pro Pack plugin and the underlying scanner used. Example: Security Pro Pack - Vulnerability Scanner v1.0.0 using Semgrep v1.10.0]`
+* **Configuration:** `[Describe any custom configurations or settings used during the scan.  If default settings were used, state that. Example: Default Semgrep ruleset was used.]`
+* **Scan Duration:** `[Specify the total time taken to complete the scan. Example: 5 minutes 30 seconds]`
 
 ## 3. Vulnerability Findings
 
@@ -26,62 +26,62 @@ This section details the vulnerabilities identified during the scan. Each vulner
 
 `[List all vulnerabilities classified as Critical.  For each vulnerability, provide the following information:]`
 
-*   **Vulnerability ID:** `[Unique identifier for the vulnerability. Example: CRITICAL-001]`
-*   **Description:** `[Detailed explanation of the vulnerability and its potential impact. Example: SQL Injection vulnerability in the login form allows attackers to execute arbitrary SQL commands.]`
-*   **Severity:** **Critical**
-*   **Location:** `[Precise location of the vulnerability in the code or configuration. Example: src/auth/login.php: line 42]`
-*   **Affected Component:** `[Specify which component or module is affected. Example: Authentication Module]`
-*   **Recommendation:** `[Specific steps to remediate the vulnerability. Example: Implement parameterized queries or use an ORM to prevent SQL injection.]`
-*   **Evidence:** `[Provide evidence of the vulnerability, such as code snippets, request/response examples, or screenshots. Example: Code snippet showing the vulnerable SQL query.]`
+* **Vulnerability ID:** `[Unique identifier for the vulnerability. Example: CRITICAL-001]`
+* **Description:** `[Detailed explanation of the vulnerability and its potential impact. Example: SQL Injection vulnerability in the login form allows attackers to execute arbitrary SQL commands.]`
+* **Severity:** **Critical**
+* **Location:** `[Precise location of the vulnerability in the code or configuration. Example: src/auth/login.php: line 42]`
+* **Affected Component:** `[Specify which component or module is affected. Example: Authentication Module]`
+* **Recommendation:** `[Specific steps to remediate the vulnerability. Example: Implement parameterized queries or use an ORM to prevent SQL injection.]`
+* **Evidence:** `[Provide evidence of the vulnerability, such as code snippets, request/response examples, or screenshots. Example: Code snippet showing the vulnerable SQL query.]`
 
 ### 3.2 High Vulnerabilities
 
 `[List all vulnerabilities classified as High.  For each vulnerability, provide the same information as in section 3.1.]`
 
-*   **Vulnerability ID:** `[Unique identifier for the vulnerability. Example: HIGH-002]`
-*   **Description:** `[Detailed explanation of the vulnerability and its potential impact. Example: Cross-Site Scripting (XSS) vulnerability allows attackers to inject malicious scripts into the website.]`
-*   **Severity:** **High**
-*   **Location:** `[Precise location of the vulnerability in the code or configuration. Example: public/js/comment.js: line 15]`
-*   **Affected Component:** `[Specify which component or module is affected. Example: Commenting System]`
-*   **Recommendation:** `[Specific steps to remediate the vulnerability. Example: Implement proper input validation and output encoding to prevent XSS.]`
-*   **Evidence:** `[Provide evidence of the vulnerability, such as code snippets, request/response examples, or screenshots. Example: Example of a malicious script being injected and executed.]`
+* **Vulnerability ID:** `[Unique identifier for the vulnerability. Example: HIGH-002]`
+* **Description:** `[Detailed explanation of the vulnerability and its potential impact. Example: Cross-Site Scripting (XSS) vulnerability allows attackers to inject malicious scripts into the website.]`
+* **Severity:** **High**
+* **Location:** `[Precise location of the vulnerability in the code or configuration. Example: public/js/comment.js: line 15]`
+* **Affected Component:** `[Specify which component or module is affected. Example: Commenting System]`
+* **Recommendation:** `[Specific steps to remediate the vulnerability. Example: Implement proper input validation and output encoding to prevent XSS.]`
+* **Evidence:** `[Provide evidence of the vulnerability, such as code snippets, request/response examples, or screenshots. Example: Example of a malicious script being injected and executed.]`
 
 ### 3.3 Medium Vulnerabilities
 
 `[List all vulnerabilities classified as Medium.  For each vulnerability, provide the same information as in section 3.1.]`
 
-*   **Vulnerability ID:** `[Unique identifier for the vulnerability. Example: MEDIUM-003]`
-*   **Description:** `[Detailed explanation of the vulnerability and its potential impact. Example: Insecure Direct Object Reference (IDOR) allows users to access resources belonging to other users.]`
-*   **Severity:** **Medium**
-*   **Location:** `[Precise location of the vulnerability in the code or configuration. Example: src/profile/profile.php: line 28]`
-*   **Affected Component:** `[Specify which component or module is affected. Example: User Profile Module]`
-*   **Recommendation:** `[Specific steps to remediate the vulnerability. Example: Implement proper authorization checks to ensure users can only access their own resources.]`
-*   **Evidence:** `[Provide evidence of the vulnerability, such as code snippets, request/response examples, or screenshots. Example: Example of a user accessing another user's profile.]`
+* **Vulnerability ID:** `[Unique identifier for the vulnerability. Example: MEDIUM-003]`
+* **Description:** `[Detailed explanation of the vulnerability and its potential impact. Example: Insecure Direct Object Reference (IDOR) allows users to access resources belonging to other users.]`
+* **Severity:** **Medium**
+* **Location:** `[Precise location of the vulnerability in the code or configuration. Example: src/profile/profile.php: line 28]`
+* **Affected Component:** `[Specify which component or module is affected. Example: User Profile Module]`
+* **Recommendation:** `[Specific steps to remediate the vulnerability. Example: Implement proper authorization checks to ensure users can only access their own resources.]`
+* **Evidence:** `[Provide evidence of the vulnerability, such as code snippets, request/response examples, or screenshots. Example: Example of a user accessing another user's profile.]`
 
 ### 3.4 Low Vulnerabilities
 
 `[List all vulnerabilities classified as Low.  For each vulnerability, provide the same information as in section 3.1.]`
 
-*   **Vulnerability ID:** `[Unique identifier for the vulnerability. Example: LOW-004]`
-*   **Description:** `[Detailed explanation of the vulnerability and its potential impact. Example: Information leakage through error messages.]`
-*   **Severity:** **Low**
-*   **Location:** `[Precise location of the vulnerability in the code or configuration. Example: config/database.php]`
-*   **Affected Component:** `[Specify which component or module is affected. Example: Database Configuration]`
-*   **Recommendation:** `[Specific steps to remediate the vulnerability. Example: Disable detailed error messages in production environments.]`
-*   **Evidence:** `[Provide evidence of the vulnerability, such as code snippets, request/response examples, or screenshots. Example: Example of an error message revealing sensitive information.]`
+* **Vulnerability ID:** `[Unique identifier for the vulnerability. Example: LOW-004]`
+* **Description:** `[Detailed explanation of the vulnerability and its potential impact. Example: Information leakage through error messages.]`
+* **Severity:** **Low**
+* **Location:** `[Precise location of the vulnerability in the code or configuration. Example: config/database.php]`
+* **Affected Component:** `[Specify which component or module is affected. Example: Database Configuration]`
+* **Recommendation:** `[Specific steps to remediate the vulnerability. Example: Disable detailed error messages in production environments.]`
+* **Evidence:** `[Provide evidence of the vulnerability, such as code snippets, request/response examples, or screenshots. Example: Example of an error message revealing sensitive information.]`
 
 ## 4. Compliance Checks
 
 `[If the scan included compliance checks, list the results here.  Specify the compliance standard being checked (e.g., PCI DSS, HIPAA, GDPR) and the status of each requirement.]`
 
-*   **Compliance Standard:** `[Specify the compliance standard. Example: PCI DSS v3.2.1]`
+* **Compliance Standard:** `[Specify the compliance standard. Example: PCI DSS v3.2.1]`
 
-    *   **Requirement 1.1.1:** `[Description of the requirement. Example: Establish and document security policies and operating procedures.]`
-        *   **Status:** `[Pass/Fail. Example: Pass]`
-        *   **Details:** `[Any relevant details about the compliance check. Example: Security policies and operating procedures are documented and reviewed annually.]`
-    *   **Requirement 2.2.2:** `[Description of the requirement. Example: Implement and maintain a firewall configuration to protect cardholder data.]`
-        *   **Status:** `[Pass/Fail. Example: Fail]`
-        *   **Details:** `[Any relevant details about the compliance check. Example: Firewall rules are not properly configured to restrict access to cardholder data.]`
+  * **Requirement 1.1.1:** `[Description of the requirement. Example: Establish and document security policies and operating procedures.]`
+    * **Status:** `[Pass/Fail. Example: Pass]`
+    * **Details:** `[Any relevant details about the compliance check. Example: Security policies and operating procedures are documented and reviewed annually.]`
+  * **Requirement 2.2.2:** `[Description of the requirement. Example: Implement and maintain a firewall configuration to protect cardholder data.]`
+    * **Status:** `[Pass/Fail. Example: Fail]`
+    * **Details:** `[Any relevant details about the compliance check. Example: Firewall rules are not properly configured to restrict access to cardholder data.]`
 
 ## 5. Recommendations
 
@@ -95,6 +95,6 @@ This section details the vulnerabilities identified during the scan. Each vulner
 
 `[Include any additional information or supporting documentation, such as links to relevant resources or detailed scan logs. Example: Links to relevant security advisories and documentation on vulnerability remediation.]`
 
-*   [Link to Security Advisories](`[Insert Link Here]`)
-*   [Link to Vulnerability Remediation Documentation](`[Insert Link Here]`)
-*   [Detailed Scan Logs (Attached Separately)]
+* Link to Security Advisories
+* Link to Vulnerability Remediation Documentation
+* [Detailed Scan Logs (Attached Separately)]

package/skills/performing-security-audits/assets/threat_model_template.md

@@ -4,16 +4,16 @@ This template is designed to help you create a comprehensive threat model for yo
 
 ## 1. Introduction
 
-*   **Project Name:** [Enter Project Name Here]
-*   **Version:** [Enter Version Number Here]
-*   **Author(s):** [Enter Author(s) Here]
-*   **Date:** [Enter Date Here]
-*   **Purpose:** [Describe the purpose of this threat model. For example: "To identify potential security threats to the [Project Name] application and outline mitigation strategies."]
+* **Project Name:** [Enter Project Name Here]
+* **Version:** [Enter Version Number Here]
+* **Author(s):** [Enter Author(s) Here]
+* **Date:** [Enter Date Here]
+* **Purpose:** [Describe the purpose of this threat model. For example: "To identify potential security threats to the [Project Name] application and outline mitigation strategies."]
 
 ## 2. System Overview
 
-*   **Description:** [Provide a high-level description of the system. What does it do? What are its key components?]
-*   **Architecture Diagram:** [Include a diagram showing the system architecture. This could be a simple block diagram or a more detailed representation.  Consider using Mermaid diagrams.]
+* **Description:** [Provide a high-level description of the system. What does it do? What are its key components?]
+* **Architecture Diagram:** [Include a diagram showing the system architecture. This could be a simple block diagram or a more detailed representation.  Consider using Mermaid diagrams.]
 
     ```mermaid
     graph LR
@@ -24,18 +24,18 @@ This template is designed to help you create a comprehensive threat model for yo
     ```
 
     [Replace the above Mermaid diagram with your actual system architecture.]
-*   **Key Components:**
-    *   [Component 1: Name, Description, Functionality]
-    *   [Component 2: Name, Description, Functionality]
-    *   [Component 3: Name, Description, Functionality]
-    *   [...]
-*   **Data Flow:** [Describe how data flows through the system. Where does data originate? Where is it stored? How is it transformed?]
+* **Key Components:**
+  * [Component 1: Name, Description, Functionality]
+  * [Component 2: Name, Description, Functionality]
+  * [Component 3: Name, Description, Functionality]
+  * [...]
+* **Data Flow:** [Describe how data flows through the system. Where does data originate? Where is it stored? How is it transformed?]
 
 ## 3. Threat Modeling Methodology
 
-*   **Methodology Used:** [Specify the threat modeling methodology used (e.g., STRIDE, PASTA, OCTAVE). If you're using a custom approach, describe it here.]
-*   **Assumptions:** [List any assumptions made during the threat modeling process. For example: "We assume that the underlying operating system is patched and up-to-date."]
-*   **Scope:** [Define the scope of the threat model. What parts of the system are included? What parts are excluded?]
+* **Methodology Used:** [Specify the threat modeling methodology used (e.g., STRIDE, PASTA, OCTAVE). If you're using a custom approach, describe it here.]
+* **Assumptions:** [List any assumptions made during the threat modeling process. For example: "We assume that the underlying operating system is patched and up-to-date."]
+* **Scope:** [Define the scope of the threat model. What parts of the system are included? What parts are excluded?]
 
 ## 4. Threat Identification
 
@@ -51,49 +51,49 @@ Use the following table to document identified threats.  Feel free to add column
 
 **Column Definitions:**
 
-*   **Threat ID:** A unique identifier for the threat.
-*   **Component:** The component of the system affected by the threat.
-*   **Threat Category:** The category of the threat (e.g., Injection, Authentication, Data Security, Availability). You can use STRIDE categories (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege) as a starting point.
-*   **Threat Description:** A detailed description of the threat.
-*   **Impact:** The potential impact of the threat if it is realized (e.g., High, Medium, Low). Consider factors like data breach, service disruption, financial loss, and reputational damage.
-*   **Likelihood:** The likelihood of the threat being realized (e.g., High, Medium, Low). Consider factors like the attacker's skill level, the attractiveness of the target, and the presence of existing security controls.
-*   **Risk Rating:** The overall risk rating, typically calculated by multiplying Impact and Likelihood (e.g., High, Medium, Low).
-*   **Mitigation Strategy:** The proposed mitigation strategy to address the threat.
-*   **Status:** The current status of the mitigation strategy (e.g., Planned, In Progress, Completed, Reviewed).
-*   **Owner:** The individual or team responsible for implementing the mitigation strategy.
+* **Threat ID:** A unique identifier for the threat.
+* **Component:** The component of the system affected by the threat.
+* **Threat Category:** The category of the threat (e.g., Injection, Authentication, Data Security, Availability). You can use STRIDE categories (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege) as a starting point.
+* **Threat Description:** A detailed description of the threat.
+* **Impact:** The potential impact of the threat if it is realized (e.g., High, Medium, Low). Consider factors like data breach, service disruption, financial loss, and reputational damage.
+* **Likelihood:** The likelihood of the threat being realized (e.g., High, Medium, Low). Consider factors like the attacker's skill level, the attractiveness of the target, and the presence of existing security controls.
+* **Risk Rating:** The overall risk rating, typically calculated by multiplying Impact and Likelihood (e.g., High, Medium, Low).
+* **Mitigation Strategy:** The proposed mitigation strategy to address the threat.
+* **Status:** The current status of the mitigation strategy (e.g., Planned, In Progress, Completed, Reviewed).
+* **Owner:** The individual or team responsible for implementing the mitigation strategy.
 
 ## 5. Data Flow Diagram (DFD) Analysis (Optional)
 
 If a Data Flow Diagram (DFD) was created, include an analysis of potential threats at each stage of the data flow.  This can supplement the table above.
 
-*   **Data Flow 1:** [Describe the data flow.  e.g., User Login]
-    *   **Process:** [Describe the process. e.g., User enters credentials on the login form.]
-        *   **Potential Threats:** [List potential threats. e.g., Credential stuffing, XSS on the login page.]
-        *   **Mitigation Strategies:** [List mitigation strategies. e.g., Rate limiting, input validation, output encoding.]
-    *   **Data Store:** [Describe the data store. e.g., Database containing user credentials.]
-        *   **Potential Threats:** [List potential threats. e.g., SQL injection, brute-force attack.]
-        *   **Mitigation Strategies:** [List mitigation strategies. e.g., Parameterized queries, account lockout policy.]
-*   **Data Flow 2:** [Describe the data flow]
-    *   [...]
+* **Data Flow 1:** [Describe the data flow.  e.g., User Login]
+  * **Process:** [Describe the process. e.g., User enters credentials on the login form.]
+    * **Potential Threats:** [List potential threats. e.g., Credential stuffing, XSS on the login page.]
+    * **Mitigation Strategies:** [List mitigation strategies. e.g., Rate limiting, input validation, output encoding.]
+  * **Data Store:** [Describe the data store. e.g., Database containing user credentials.]
+    * **Potential Threats:** [List potential threats. e.g., SQL injection, brute-force attack.]
+    * **Mitigation Strategies:** [List mitigation strategies. e.g., Parameterized queries, account lockout policy.]
+* **Data Flow 2:** [Describe the data flow]
+  * [...]
 
 ## 6. Security Requirements
 
 Based on the identified threats, define specific security requirements for the system.
 
-*   **Requirement 1:** [e.g., Implement multi-factor authentication for all user accounts.]
-    *   **Justification:** [e.g., Mitigates the risk of unauthorized access due to compromised credentials.]
-*   **Requirement 2:** [e.g., Encrypt all sensitive data at rest and in transit.]
-    *   **Justification:** [e.g., Protects data from unauthorized disclosure in case of a data breach.]
-*   **Requirement 3:** [e.g., Regularly scan the application for vulnerabilities.]
-    *   **Justification:** [e.g., Identifies and addresses potential security flaws before they can be exploited.]
+* **Requirement 1:** [e.g., Implement multi-factor authentication for all user accounts.]
+  * **Justification:** [e.g., Mitigates the risk of unauthorized access due to compromised credentials.]
+* **Requirement 2:** [e.g., Encrypt all sensitive data at rest and in transit.]
+  * **Justification:** [e.g., Protects data from unauthorized disclosure in case of a data breach.]
+* **Requirement 3:** [e.g., Regularly scan the application for vulnerabilities.]
+  * **Justification:** [e.g., Identifies and addresses potential security flaws before they can be exploited.]
 
 ## 7. Conclusion
 
-*   **Summary of Findings:** [Summarize the key findings of the threat model.]
-*   **Recommendations:** [Provide recommendations for improving the security of the system.]
-*   **Next Steps:** [Outline the next steps to be taken, such as implementing the mitigation strategies and security requirements.]
+* **Summary of Findings:** [Summarize the key findings of the threat model.]
+* **Recommendations:** [Provide recommendations for improving the security of the system.]
+* **Next Steps:** [Outline the next steps to be taken, such as implementing the mitigation strategies and security requirements.]
 
 ## 8. Appendix (Optional)
 
-*   **Glossary of Terms:** [Define any technical terms used in the threat model.]
-*   **References:** [List any relevant references, such as security standards, best practices, or vendor documentation.]
+* **Glossary of Terms:** [Define any technical terms used in the threat model.]
+* **References:** [List any relevant references, such as security standards, best practices, or vendor documentation.]

package/skills/performing-security-audits/references/README.md

@@ -1,4 +1,3 @@
 # References
 
 Bundled resources for security-pro-pack skill
-

package/skills/performing-security-audits/scripts/{security_scan.sh → security_scan.py}

@@ -5,12 +5,11 @@ Automates running various security scans (e.g., nmap, nessus) and parsing the re
 Generated: 2025-12-10 03:48:17
 """
 
-import os
 import sys
 import json
 import argparse
 from pathlib import Path
-from datetime import datetime
+
 
 def process_file(file_path: Path) -> bool:
     """Process individual file."""
@@ -24,7 +23,7 @@ def process_file(file_path: Path) -> bool:
     # This is a template that can be customized
 
     try:
-        if file_path.suffix == '.json':
+        if file_path.suffix == ".json":
             with open(file_path) as f:
                 data = json.load(f)
             print(f"  ✓ Valid JSON with {len(data)} keys")
@@ -37,12 +36,13 @@ def process_file(file_path: Path) -> bool:
         print(f"  ✗ Error: {e}")
         return False
 
+
 def process_directory(dir_path: Path) -> int:
     """Process all files in directory."""
     processed = 0
     failed = 0
 
-    for file_path in dir_path.rglob('*'):
+    for file_path in dir_path.rglob("*"):
         if file_path.is_file():
             if process_file(file_path):
                 processed += 1
@@ -51,28 +51,29 @@ def process_directory(dir_path: Path) -> int:
 
     return processed, failed
 
+
 def main():
     parser = argparse.ArgumentParser(
         description="Automates running various security scans (e.g., nmap, nessus) and parsing the results."
     )
-    parser.add_argument('input', help='Input file or directory')
-    parser.add_argument('--output', '-o', help='Output directory')
-    parser.add_argument('--verbose', '-v', action='store_true', help='Verbose output')
-    parser.add_argument('--config', '-c', help='Configuration file')
+    parser.add_argument("input", help="Input file or directory")
+    parser.add_argument("--output", "-o", help="Output directory")
+    parser.add_argument("--verbose", "-v", action="store_true", help="Verbose output")
+    parser.add_argument("--config", "-c", help="Configuration file")
 
     args = parser.parse_args()
 
     input_path = Path(args.input)
 
-    print(f"🚀 security-pro-pack - security_scan.sh")
-    print(f"   Category: packages")
-    print(f"   Plugin: security-pro-pack")
+    print("🚀 security-pro-pack - security_scan.sh")
+    print("   Category: packages")
+    print("   Plugin: security-pro-pack")
     print(f"   Input: {input_path}")
 
     if args.config:
         if Path(args.config).exists():
             with open(args.config) as f:
-                config = json.load(f)
+                json.load(f)
             print(f"   Config: {args.config}")
 
     # Process input
@@ -81,7 +82,7 @@ def main():
         result = 0 if success else 1
     elif input_path.is_dir():
         processed, failed = process_directory(input_path)
-        print(f"\n📊 SUMMARY")
+        print("\n📊 SUMMARY")
         print(f"   ✅ Processed: {processed}")
         print(f"   ❌ Failed: {failed}")
         result = 0 if failed == 0 else 1
@@ -96,5 +97,6 @@ def main():
 
     return result
 
+
 if __name__ == "__main__":
     sys.exit(main())