cursor-rules-review
Pass
Audited by Gen Agent Trust Hub on Mar 29, 2026
Risk Level: SAFE
Full Analysis
- [COMMAND_EXECUTION]: Standard Unix utilities are used to perform static audits of local rule files. \n
- Evidence: Use of
find,grep,ls,head, andwcacrossSKILL.mdandreferences/CHECKLIST.mdto validate YAML frontmatter, file length, and cross-references. \n - Security: Parsing of file content in the provided shell snippets (e.g., in
references/CHECKLIST.md) is constrained by restrictive regular expressions like[a-z-]*, which mitigates the risk of command injection from maliciously crafted rule files. \n - Context: The use of
cat .cursor/settings.jsoninreferences/TROUBLESHOOTING.mdis appropriate for debugging IDE-specific configuration issues related to rule triggering.- [DATA_EXFILTRATION]: There is no evidence of network communication or data transmission to external servers. All operations are local to the project environment.- [PROMPT_INJECTION]: The skill instructions define a procedural audit workflow and do not contain patterns typical of jailbreaking, safety bypass, or instruction override.
Audit Metadata