Security audit
Security checks for vulnerabilities and agentic risk
This SEO skill is a straightforward website-audit helper with local analysis scripts and no evidence of hidden, persistent, or unrelated behavior.
Install this only if you want the agent to inspect and edit SEO-related website files. Review generated sitemap, robots.txt, schema, and language metadata before publishing, especially for non-English or multilingual sites.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
Missing or Poor Title Tags:
<!-- Add unique, descriptive title to <head> -->
<title>Primary Keyword - Secondary Keyword | Brand Name</title>
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!-- Good -->
<img src="responsive-web-design-example.jpg"
alt="Responsive web design showing mobile, tablet, and desktop layouts">
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
The phrase "Any task related to search engine optimization for HTML/CSS websites" is broad and lacks clear boundaries or exclusions. In a manifest/markdown trigger section, this can cause unintended invocation for loosely related website tasks that mention SEO only peripherally.
The guidance hard-codes <html lang="en"> as the recommended fix for missing language metadata. This imposes English regardless of the website's actual language and does not offer user choice or context-specific selection.
The Organization schema example hard-codes "availableLanguage": "English", which can be read as prescribing a specific language/locale. Under the policy, forced language defaults without opt-in or justification can be a natural-language policy issue, even when embedded in example content.
The example <html lang="en"> is presented under 'Requirements' for language declaration, which can be read as mandating English rather than using the site's actual language. This is a natural-language locale policy concern because the document does not clearly state that the language code should match the page's intended language or user locale.
No suspicious patterns detected.