Security audit
Security checks for vulnerabilities and agentic risk
This is a rental-advice skill made of Markdown guidance; it has some privacy and legal-safety caveats but no hidden execution, persistence, or data access behavior.
Reasonable to install for rental help, but treat legal, credit/background screening, and access-code guidance as prompts to verify local rules and use secure channels. Do not share applicant documents, Wi-Fi passwords, lockbox codes, or full addresses more broadly than necessary.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
## Session State
<!-- active_role: tenant | landlord | host | guest | equipment -->
<!-- current_search: location, budget, requirements -->
<!-- properties: addresses being tracked -->
The tenant-screening section instructs landlords to collect and evaluate highly sensitive personal data, including government ID, income, credit, background, landlord references, and employment information, but it does not mention obtaining applicant consent, complying with screening and privacy laws, securing the data, limiting retention, or avoiding discriminatory use. In a rental skill, this omission can lead users to perform unlawful or unsafe screening practices that expose applicants to privacy harm, misuse of personal information, and legal violations.
The templates encourage sharing sensitive operational details such as a full address, entry/access instructions, Wi‑Fi credentials, and a phone number in generic message text without any guidance on limiting disclosure to confirmed guests or using platform-protected channels. If copied into unsafe contexts, this can enable unauthorized access, privacy violations, social engineering, or compromise of the property network.
No suspicious patterns detected.