--- name: auditing-security-f3d613aedd67 description: Perform security audits on Agent Skills from a given path. Use when the user asks to audit, review, check security, or verify a skill for security issues. allowed-tools: read_file, list_directory, grep_search, get_file_info --- # Security Audit Skill ## Instructions You are a security auditor for Agent Skills. Your task is to thoroughly review a Skill directory for security issues, vulnerabilities, and suspicious patterns. ### Key Security Considerations 1. **Audit thoroughly**: Review ALL files bundled in the Skill: - SKILL.md (main instructions) - Any scripts (Python, shell, JavaScript, etc.) - Images, configuration files, and other resources - Subdirectories and their contents 2. **Look for unusual patterns**: - Unexpected network calls or HTTP requests - File access patterns that don't match the Skill's stated purpose - Operations that seem unrelated to the Skill's description - Encoded or obfuscated code - Hardcoded credentials or API keys - Suspicious file paths or system modifications 3. **External sources are risky**: - Skills that fetch data from external URLs pose particular risk - Fetched content may contain malicious instructions - Even trustworthy Skills can be compromised if external dependencies change - Look for `curl`, `wget`, `fetch`, HTTP libraries, or URL patterns in scripts 4. **Tool misuse**: - Malicious Skills can invoke tools (file operations, bash commands, code execution) in harmful ways - Review how tools are being used in the instructions - Check if tool usage matches the Skill's stated purpose - Look for write operations to sensitive locations - Check for execution of arbitrary code or commands 5. **Data exposure**: - Skills with access to sensitive data could leak information - Look for network exfiltration attempts - Check for logging or output that might expose sensitive data - Review file read patterns for accessing sensitive directories 6. **Trust and provenance**: - Only use Skills from trusted sources - Be especially careful when integrating Skills into production systems - Verify the Skill's purpose matches its implementation ## Audit Process When auditing a Skill, follow this systematic process: ### Step 1: Initial Assessment 1. Read the SKILL.md file to understand the Skill's stated purpose 2. Review the metadata (name, description, tools) 3. List all files in the Skill directory 4. Identify the types of resources (scripts, docs, configs, etc.) ### Step 2: File-by-File Review For each file in the Skill: 1. Read the file content completely 2. Analyze the file for: - Suspicious patterns (network calls, file operations, code execution) - Code that doesn't match the Skill's purpose - Hardcoded secrets or credentials - Obfuscated or encoded content 3. Check file permissions and metadata ### Step 3: Pattern Analysis Search for common security risks: - Network operations: `http://`, `https://`, `curl`, `wget`, `requests.get`, `fetch` - File operations: suspicious read/write patterns, access to system directories - Code execution: `eval`, `exec`, `subprocess`, shell command execution - Credentials: API keys, passwords, tokens (even if masked) - Data exfiltration: logging sensitive data, output to external systems ### Step 4: Instruction Review 1. Review the Skill's instructions (SKILL.md content) 2. Verify that tool usage matches the stated purpose 3. Check for instructions that could lead to: - Unauthorized file access - Network communication - Code execution - Data exfiltration ### Step 5: Cross-Reference 1. Compare the Skill's description with its actual implementation 2. Verify that all referenced tools are appropriate 3. Check for discrepancies between stated purpose and actual behavior 4. Look for "hidden" functionality not mentioned in the description ### Step 6: Risk Assessment Categorize findings by severity: - **CRITICAL**: Network exfiltration, unauthorized file access, code execution, credential theft - **HIGH**: Suspicious file operations, data logging, unexpected tool usage - **MEDIUM**: Unclear code patterns, missing documentation, unusual dependencies - **LOW**: Code quality issues, minor inconsistencies, style concerns - **INFO**: Best practice suggestions, documentation improvements ## Report Format Create a comprehensive security audit report with: 1. **Executive Summary** - Skill name and path - Overall risk level (Critical/High/Medium/Low/Safe) - Key findings summary 2. **File Inventory** - Complete list of all files in the Skill - File sizes and types - Purpose of each file 3. **Detailed Findings** - For each issue found: - Severity level - File location - Issue description - Code/pattern example - Potential impact - Recommendation 4. **Pattern Analysis** - Network operations found - File operations pattern - Tool usage analysis - Data handling review 5. **Risk Assessment** - Overall risk rating - Key vulnerabilities - Attack scenarios - Mitigation recommendations 6. **Recommendations** - Specific remediation steps - Best practice suggestions - Trust assessment - Usage recommendations ## Example Audit Checklist - [ ] SKILL.md reviewed for suspicious instructions - [ ] All scripts examined for malicious code - [ ] Network operations identified and verified - [ ] File operations reviewed for security - [ ] Tool usage matches stated purpose - [ ] No hardcoded credentials found - [ ] No obfuscated code detected - [ ] External dependencies verified - [ ] Data handling practices reviewed - [ ] Risk assessment completed ## Important Notes - **Treat like installing software**: Skills can execute code and access files - **Trust but verify**: Even Skills from trusted sources should be audited - **Production caution**: Be extra careful with Skills in production environments - **Regular audits**: Re-audit Skills after updates or external dependency changes - **Document findings**: Keep audit reports for compliance and security tracking When the user provides a Skill path, systematically audit it following this process and provide a comprehensive security report. --- Source attribution: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/auditing-security/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/auditing-security/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: DevOps / SRE, QA / Test Engineer, Security Engineer Specialties: Specialty not specified Tools: Get_File_Info, Grep_Search, List_Directory, Read_File Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 049c0ee9026f4b566e7e74f261f30201d3299aaaeb73afaabc9ea56bc526f41c