Back to skill

Security audit

Context Doctor

Security checks for vulnerabilities and agentic risk

Overview

This is a transparent context-usage diagnostic skill, with only a minor caveat that some trigger words are broad enough to activate unintentionally.

Use explicit phrases like “context doctor” if you want to avoid accidental activation. Before installing, be comfortable with the agent summarizing session metadata such as token usage, model/cost data, tool-call counts, and large-output rankings; avoid enabling heartbeat auto-checks unless you want periodic reports.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (6)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The trigger phrase "诊断" is very broad in normal conversation and can easily appear in unrelated user requests, causing unintended activation of the skill. In a skill that inspects session state and reports token/context usage, accidental invocation can waste context, reveal conversation metadata, and interfere with the agent's intended task flow.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The phrase "checkup" is generic English vocabulary and may be used in ordinary conversation unrelated to context diagnostics. This raises the risk of unintentional skill execution, which can consume tokens, interrupt workflow, and expose session-level metadata when the user did not intend to request it.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The trigger list includes very generic phrases like “诊断” and “健康检查”, which can match ordinary conversation and cause the skill to activate outside the user’s intended scope. In an agent setting, ambiguous activation can lead to unnecessary introspection about session state, extra token consumption, and accidental disclosure of operational metadata when the user did not explicitly request this skill.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The file consistently specifies the skill in Chinese and presents the report format, labels, and operating guidance only in Chinese, with no indication that the response language should follow user preference. This can create a locale-policy issue if the organization expects language choice or user opt-in rather than a fixed language.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The usage guidance repeats broad activation conditions such as “体检” and “诊断” without defining boundaries, reinforcing accidental triggering during normal conversation. Because this skill inspects session/tool usage state, mistaken activation can consume more context and expose conversation-structure metadata that may not be relevant or desired.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
77% confidence
Finding

The documentation is presented only in Chinese and English, with no indication that the skill supports or adapts to the user's preferred language or locale. For a language/locale policy review, this can be read as an implicit two-language constraint without opt-in or justification.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.