Tp2
- Category
- MCP Tool Poisoning
- Confidence
- 85% confidence
- Finding
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
- Content
Security audit
Security checks for vulnerabilities and agentic risk
The skill does not contain code or destructive behavior, but its broad activation and unrelated merged content make it likely to trigger in the wrong context.
Install only if you are comfortable with a low-capability but messy learning note that may activate on broad Agent-related prompts. It should be narrowed to specific Agent-development tutorial triggers and split from unrelated PS Portal or game-review content before normal use.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The trigger includes extremely broad phrases such as 'Agent开发' and especially 'Agent', which are likely to match ordinary conversation and unintentionally activate this skill. Because the skill content is already inconsistent, broad triggering makes the confusion more dangerous by increasing the chance of accidental invocation in unrelated contexts.
The activation scenarios are vague ('用户说"Agent"' and general requests for Agent development help), which does not sufficiently constrain when the skill should run. In combination with duplicated and contradictory content, ambiguous activation increases the risk of the wrong instructions being surfaced or trusted during normal user conversations.
The manifest presents this as an Agent development learning skill, but later content shifts into unrelated gaming/device review material, creating a mismatch between declared purpose and actual instructions. In agent ecosystems, this is dangerous because routing and trust decisions are often based on manifest metadata; misleading metadata can trigger the wrong capability in response to common user requests.
The file redefines the same skill as unrelated PS Portal/SonyAgent content inside the documentation, which creates instruction ambiguity and weakens trust boundaries for downstream agents selecting or executing skills. This kind of content drift can cause the wrong skill to activate or supply irrelevant behavior under a trusted Agent-development label, increasing the risk of prompt confusion, misrouting, or unintended actions.
No suspicious patterns detected.