Back to skill

Security audit

决策架构师

Security checks for vulnerabilities and agentic risk

Overview

This decision-support skill is not clearly malicious, but it asks for broad local authority and gives contradictory guidance about command execution, network/API use, and local memory.

Review this before installing. The skill appears to be a local decision aid, but it should not need shell execution, broad filesystem search, API credentials, or network setup. Install only if you can restrict exec and filesystem access, are comfortable with local storage of decision preferences and history, and can inspect or delete $HOME/decision-architect/ records.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • 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
Findings (1)

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
SKILL.md:23
Finding

Unnecessary Command-Execution Privilege

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:23-29
Vulnerability Type: Excessive tool permissions and violation of least privilege
Risk Level: Medium

yaml
tools:
- read
- exec
- write
- glob
- grep
homepage: ''

The declared capability conflicts with the Skill's own statements at SKILL.md:210-211:

text
**API Key configuration:** This Skill does not require an API key. It is driven entirely by Markdown instructions, stores all memory locally under `$HOME/decision-architect/`, and makes no network requests.
**Availability classification:** MD (pure Markdown instructions with no need for exec command-line capability).

Technical Analysis

The Skill requests the exec tool even though it explicitly states that command-line execution is unnecessary. Its documented functionality consists of decision analysis and local Markdown-based state management, for which narrowly scoped file-reading and file-writing capabilities are sufficient.

Providing shell execution violates the principle of least privilege. Although the audited instructions do not explicitly invoke commands or contain a malicious payload, the unnecessary capability expands the consequences of prompt injection, malformed user input, or future instruction changes. An Agent that interprets attacker-controlled decision text as operational instructions could use exec to run commands outside the legitimate decision-analysis workflow.

Attack Path

  1. The Skill is loaded with the declared exec permission.
  2. An attacker supplies decision-related content containing adversarial instructions that attempt to induce command execution.
  3. The Agent incorrectly treats those instructions as part of the Skill workflow.
  4. Because shell execution is already authorized, the Agent invokes exec.
  5. The command runs with the operating-system privileges and environmental access of the Agent process.

This is an enabling atta ...[truncated 608 chars]

Remediation
View remediation

Remediation Suggestions

  1. Remove exec from the declared tools list because the documented workflow does not require shell commands.
  2. Retain only capabilities necessary for the workflow, such as read and write.
  3. Restrict write access to the documented $HOME/decision-architect/ directory rather than granting unrestricted filesystem writes.
  4. Remove glob and grep unless a concrete workflow requires them; otherwise, constrain their search scope to the Skill's designated data directory.
  5. Enforce runtime authorization for sensitive tool calls so user-supplied content cannot independently trigger shell or unrestricted filesystem operations.
  6. Treat all decision text and persisted records as untrusted data, not executable Agent instructions.
  7. Remove the optional callback_url parameter at SKILL.md:99 if networking is unsupported, or document and implement strict HTTPS-only URL validation, destination allowlisting, private-address blocking, redirect controls, and explicit user approval before callbacks.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (7)

Intent-Code Divergence

High
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill makes materially inconsistent claims about its capabilities: it says it is pure Markdown with no command execution or network requests, yet declares the exec tool and includes sections about command execution, TLS, API keys, and API calls. This can mislead users and host agents into granting broader trust or permissions than warranted, increasing the chance of unsafe execution paths being enabled under false assumptions.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

High
Category
Not specified by scanner
Confidence
96% confidence
Finding

The capability-boundary section states the skill does not access external systems or sensitive data, but later installation and error-handling sections instruct users to configure API keys and establish API connections. Such contradictions undermine informed consent and can cause operators to expose credentials or permit outbound access for a skill they believed was self-contained and non-networked.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The activation guidance is extremely broad, covering general AI model use, intelligent dialogue, agent orchestration, and LLM applications. Overbroad triggers can cause the skill to activate in many unrelated contexts, increasing unintended access to user inputs, local files, and persistent memory, especially given the declared read/write/exec capabilities.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill describes persistent storage of decision preferences, reversals, and historical records in local files, but does not present a prominent privacy notice, retention policy, or explicit consent mechanism. For a tool that profiles user risk preferences and decision style, silent persistence can expose sensitive behavioral data and create privacy harm even without external exfiltration.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The keyword list includes vague everyday phrases such as should, 怎么办, pros, cons, decision, and tradeoff without strong contextual constraints. This can make the skill over-trigger on ordinary conversations, leading to unnecessary analysis, memory writes, or exposure of contextual data beyond what the user reasonably expected.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
87% confidence
Finding

For a decision-support skill described as local structured analysis with local memory, the API/network setup and troubleshooting guidance introduces unjustified external connectivity. Even if not overtly malicious, unnecessary network capability expands the attack surface, raises data leakage risk, and can normalize credential provisioning where none should be needed.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
84% confidence
Finding

The skill metadata and almost all user-facing instructions are presented in Chinese, but the document does not state that language is configurable or that Chinese is required for a justified region-specific purpose. This can amount to an implicit language policy constraint without user opt-in.

Content

No source excerpt is available for this finding.