Security audit

Yaohx Expense Tracker

Security checks for vulnerabilities and agentic risk

Overview

This is a local expense-tracking skill with sensitive but clearly purpose-aligned bookkeeping behavior and no evidence of hidden exfiltration or unsafe installation.

Install only if you are comfortable keeping expense history in local workspace files. Review or redact payment screenshots before sharing them, and be careful with deletion requests because the documented flow does not describe undo or a mandatory confirmation step.

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (4)

Vague Triggers

Medium

Confidence: 89% confidence
Finding: The trigger phrases include broad everyday expressions such as spending, bills, and monthly summaries, which can cause the skill to activate on ordinary financial discussion rather than an explicit bookkeeping request. In this context, unintended activation is risky because the skill handles sensitive expense data and may prompt for or process payment screenshots and local financial records without sufficiently clear user intent.

Vague Triggers

Medium

Confidence: 86% confidence
Finding: The activation scenarios describe many expense-related situations but do not clearly state when the skill should not trigger, such as casual discussion of prices, budgeting advice, or general conversation about spending. Because the skill can write, delete, and summarize local financial data, missing boundaries increase the chance of accidental data modification or exposure of private spending history.

Missing User Warnings

Medium

Confidence: 93% confidence
Finding: The skill encourages users to send payment screenshots for OCR but does not warn that these images may contain sensitive personal or financial information such as names, account identifiers, transaction details, or balances. Even though processing is described as local-only, users still need clear notice before sharing high-sensitivity data so they can make an informed decision and redact unnecessary content.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The deletion workflow allows removing records by ID and examples include deleting the most recent record, but there is no explicit warning about irreversible data loss or a mandatory confirmation step. In a bookkeeping context, accidental deletion can permanently remove financial history and undermine report accuracy, especially when triggered from ambiguous user phrasing like 'delete that one'.

Static analysis

No suspicious patterns detected.