T02 · Agent Memory Poisoning
- Location
SKILL.md:215- Finding
Persistent Skill Self-Modification from User-Controlled Feedback
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This business-plan skill has a coherent purpose, but it asks agents to persistently edit the skill itself and read project memory/logs, which users should review before installing.
Install only if you are comfortable with a business-plan assistant that may edit its own skill instructions, read project memory/logs during update requests, and use external document-upload tooling. Safer use would require disabling automatic SKILL.md edits, confirming exact memory files before reading them, pinning dependencies, and requiring explicit approval before cloud uploads or knowledge-base storage.
SKILL.md:215Persistent Skill Self-Modification from User-Controlled Feedback
SKILL.md:217Overbroad Collection of Persistent Agent Memory and Session History
SKILL.md:204Unpinned Installation of the Pillow Dependency
SKILL.md:109Execution of Unbundled Scripts from an External Skill
The auto-load trigger is broad enough to activate on ordinary business-plan-related discussion, causing the skill to run even when the user did not explicitly request it. Unintended invocation increases the chance of unnecessary file access, persistence behavior, or workflow actions being applied outside the intended scope.
The skill requires the agent to edit its own SKILL.md after routine task completion, creating a self-modifying instruction set without strong approval boundaries. This can let untrusted task output or user feedback persist into future runs, causing prompt drift, policy bypass, or propagation of unsafe behavior across sessions.
Referenced artifact was not completely inspected
2. 依据反馈,用 **Edit** 直接更新本 `SKILL.md`:
The intake section states the target market defaults to North America, which bakes in a locale/region assumption into the workflow. Because this default is not framed as an opt-in choice or justified as a region-specific compliance tool, it can violate the policy against forcing a locale without user selection.
The skill recommends storing reusable assets and project knowledge in knowledge bases or local files, which can retain user-provided content beyond the immediate task and make it accessible later in unintended contexts. Even if intended for convenience, persistent storage of BP materials can include sensitive business strategy, financial assumptions, or competitive analysis.
Reading project memory and daily logs across sessions can expose historical user-provided data that is unrelated to the current request. In the context of a BP-authoring skill, this is more dangerous because the workflow does not inherently require broad retrospective access, so the extra data collection is disproportionate and creates avoidable privacy risk.
The skill instructs the agent to read .workbuddy/memory/ including MEMORY.md and daily logs across sessions, which exceeds the narrow needs of drafting a business plan and can expose unrelated prior user data. Cross-session memory access expands the data surface and may leak sensitive information from earlier projects into the current task.
The skill tells the agent to modify SKILL.md after each task without a prominent user-facing warning that the skill file itself will be altered. Hidden modification of system behavior is dangerous because it changes future execution state and may preserve unsafe or task-specific instructions beyond the user's awareness.
The file claims the public release removed private paths and credential paths, but the body still references local memory paths and credentialed integrations. This mismatch can mislead reviewers and operators into underestimating privacy and secret-handling risks, increasing the chance of unsafe deployment or trust in inaccurate documentation.
The trigger phrase "BP" is highly ambiguous and can match many unrelated user intents, causing the skill to activate outside its intended business-planning context. Over-broad activation can route users into the wrong workflow, create prompt/skill hijacking opportunities, and increase the chance of inappropriate data collection or unintended task execution.
The trigger "business plan" is broad and overlaps with common, generic requests, so the skill may be invoked for many contexts beyond this specialized methodology. This increases accidental activation risk and can expose users to irrelevant or unintended behavior when they were not asking for this specific skill.
The manifest includes Chinese-only description content and several Chinese trigger phrases, but does not state whether language choice is user-selectable or optional. This may create an implicit language/locale preference without explicit opt-in, which can conflict with language-choice policy expectations.
No suspicious patterns detected.