Security audit
Security checks for vulnerabilities and agentic risk
This skill is a documentation workflow for an Obsidian vault and does not show hidden code execution, credential access, exfiltration, or persistence behavior.
Before installing, confirm this skill is used only with the intended Obsidian documentation vault and that its English-primary language policy matches your team’s expectations. Review archive or move operations before applying them to important notes.
The skill explicitly requires documents to use English primarily and to translate/summarize Persian content in English, but there is no user opt-in or allowance for user language preference. In an agent setting, this can override user intent, distort meaning for multilingual content, and cause unauthorized transformation of user-provided text.
The Chinese section repeats the same mandatory English-primary requirement and requires Persian content to be translated/summarized into English without user consent. Duplicating the rule in another language reinforces that the behavior is intentional and increases the likelihood an agent will ignore user language preferences consistently.
Lines L149-L151 state that all documents use English as the primary language and that Persian content must be translated or summarized in English. This is a natural-language locale policy constraint presented as a blanket rule, with no user opt-in or documented justification for a region-specific requirement.
This markdown file is in scope for vague-trigger review, and the example links [[About auth]] and [[Auth flow in Project-1]] are broad natural-language phrases that resemble ordinary prose rather than narrowly scoped conventions. Because the document presents them as a reusable template pattern without negative examples or specificity constraints, it could encourage ambiguous references or unintended matching in systems that activate on document titles or phrases.
The file is primarily written in English, but lines L256-L267 introduce Chinese text ('筛选条件') in section labels. This imposes a mixed-language convention without any user opt-in or justification that the document is intended for a Chinese-speaking or region-specific audience.
This file is documentation for tagging behavior, and L280 explicitly says 'Contradictory standards' even though the sentence that follows describes alignment and consistency between tags and frontmatter fields. That wording directly conflicts with the documented intent of the section and could mislead an agent consuming the guidance.
