T09 · Insecure Skill Coding Practices
- Location
SKILL.md:394- Finding
Sensitive Configuration Values May Be Propagated into Generated Documentation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a real documentation skill, but it should be reviewed because it can scan source/config files and write persistent docs that may expose sensitive values.
Install only for repositories you are allowed to scan. Add or keep .ai-doc in .gitignore, review and redact generated documentation before sharing or committing it, and do not confirm migration, merge, delete, or restore actions until you have reviewed the plan. Avoid running it on untrusted repositories unless the agent environment can confine subagents to the intended project files and output directory.
SKILL.md:394Sensitive Configuration Values May Be Propagated into Generated Documentation
references/subagent-task-template.md:8Untrusted Repository Content Is Delegated to Subagents Without Prompt-Injection Isolation
This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.
**Rationale**: Bash references suggested alternative file-reading strategies that could bypass security controls.
---
The changelog explicitly documents a past feature described as a 'Security workaround' using bash-based reading of protected files. Even though this is historical documentation and later versions claim to remove or rename it, recording that capability in a skill focused on file analysis strongly suggests the skill may have included or normalized access-control bypass behavior, which is dangerous in this context because the skill operates over source trees and documentation files where unauthorized reads could expose secrets or restricted project content.
The README explicitly describes writing generated documentation, logs, and state files into the target project's .ai-doc directory, but it does not clearly warn users that the skill will modify the analyzed repository. In a documentation-generation skill, silent filesystem modification can lead to unintended workspace changes, accidental commits of generated artifacts, or pollution of production repositories, especially when users expect read-only analysis.
The file consistently presents its operational instructions, prompts, and user interaction text in Chinese, including confirmation prompts and usage examples. This can amount to forcing a specific language/locale without explicitly offering the user a choice or documenting a justified region-specific constraint.
The activation trigger includes a broad phrase like '理解这个工程', which can match routine conversation and cause the skill to activate unexpectedly. In this skill's context, activation can lead to large-scale project scanning, file enumeration, and potential follow-on write operations under .ai-doc, so accidental invocation increases the risk of unintended analysis and workspace modification.
SQP-3 applies to all file types and covers language or locale policy violations. This markdown file presents all headings, descriptions, and usage guidance in Chinese only, with no indication that users may select another language or that the document is intentionally limited to a Chinese-only regional context.
The natural-language description is entirely in Chinese and presents the skill as a general-purpose Java Maven documentation generator, but it does not indicate that the Chinese locale is optional or region-specific. For a generally applicable skill, this can violate language/locale policy by implicitly forcing a specific language without user opt-in.
This markdown guide presents all instructions, prompts, and examples exclusively in Chinese, which can amount to a language/locale policy violation when no user opt-in or alternative language path is provided. The document does not state that the skill is region-specific or otherwise justified to require Chinese only.
This markdown file presents all operational instructions in Chinese and does not indicate that users may choose another language or that the skill is intended only for a Chinese-speaking or region-specific context. That creates a natural-language policy concern because it effectively forces a specific language without user opt-in.
The natural-language content consistently forces a specific language/locale for the skill guidance, and there is no indication that users can opt into another language. Under the stated policy, fixed-language behavior should either offer user choice or clearly justify a region-specific constraint.
This markdown file is entirely presented in Chinese from the title onward, with no indication that the user can choose another language or that the locale restriction is required for a region-specific purpose. The policy explicitly calls for flagging language or locale constraints that are imposed without user opt-in.
Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.
$retryPolicy = @{ MaxRetries = 0 }
The entire skill template is written as a mandatory Chinese-language task format, including headings, instructions, and example outputs, with no indication that users may choose another language or locale. This creates a natural-language policy concern because it implicitly forces a specific language across all generated documentation without opt-in.
This markdown file includes a recovery step that copies a backup over .ai-doc/.generate-state.json, which is a file write operation that can discard newer task-state information. While it describes the action, it does not provide a user warning about potential loss of current progress metadata or advise verifying the backup before replacement.
These lines tell the user to manually update the state file and mark subagents as failed, which can alter execution state and affect resume/retry behavior. The document does not warn that manual state edits may corrupt task tracking or cause incorrect recovery decisions if done improperly.
This markdown template is written entirely in Chinese and defines all section headings and labels in Chinese, which effectively constrains generated documentation to a specific language. The policy allows locale constraints only when the skill offers user choice or clearly documents a justified region-specific requirement, neither of which is present here.
This markdown template is entirely written in Chinese, including all headings, labels, and instructional placeholders, which implies the generated documentation will be produced in a fixed language. Under the policy criteria, forcing a specific language without offering user choice or documenting a justified locale restriction is a natural-language policy violation.
This markdown template uses Chinese as the required document language in its title and throughout all section headings and instructions. The file does not offer a language choice or explain why Chinese is mandatory, which creates a locale policy issue under the natural-language policy rules.
This markdown file is in scope for natural-language policy checks. The entry states that the SKILL.md description field was changed to English to avoid garbled text, which suggests a forced language choice rather than offering users a language/locale option or documenting a justified locale constraint.
The README presents the skill's natural-language usage and behavior in Chinese, but does not indicate that users may choose another language or that the skill is intentionally restricted to a Chinese-speaking audience. Under the policy, forcing a specific language without user opt-in is a natural-language policy concern.
This markdown file includes operational guidance and examples in Chinese, and the document does not indicate that the language is optional or user-selected. Under the stated policy, forcing a specific language or locale without opt-in can be a natural-language policy violation.
The file presents safety instructions and prohibitions in Chinese, but does not say the skill or document is intended specifically for Chinese-speaking users. Because the policy applies to all file types, untranslated or single-locale guidance can be flagged when no user choice or justification is given.
At L0123-L0124 and L0175-L0196, the skill explicitly documents a safety constraint that migration or merge operations must only occur after asking the user and receiving confirmation. The summary bullet at L0965 says '文档迁移:自动合并已存在文档', which contradicts that safer behavior by describing the operation as automatic.
The workflow at L0123-L0124 and L0168-L0196 repeatedly states that any migration, merge, or deletion-related action requires explicit user confirmation first. However, the example at L0984 presents migration/merge as an immediate execution step, which conflicts with the documented safety requirement and may mislead implementers about intended behavior.
This markdown file is written exclusively in Chinese, including headings, descriptions, and operational notes. Under the policy rule for natural-language violations, forcing a specific language without user opt-in or clear justification can be a locale policy issue.