Back to skill

Security audit

Client Project Tracker

Security checks for vulnerabilities and agentic risk

Overview

This is a local CRM-style skill that stores client and project records as advertised, with privacy caveats but no evidence of hidden execution or data exfiltration.

Install only if you are comfortable keeping client contact details, project notes, invoice amounts/status, and communication summaries in a local client-data.json file. Avoid storing secrets, card or bank details, regulated personal data, or unnecessary confidential notes, and periodically review or delete the data file when client information should not be retained.

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 (3)

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The README explicitly promotes storing client contact details, communication preferences, relationship notes, invoices, and project history, all of which can include personal, financial, or confidential business information, but provides no privacy, retention, access-control, or secure-handling guidance. In a freelancer/consultant CRM context, this omission increases the chance that users will collect and persist sensitive data insecurely, leading to privacy breaches or unauthorized disclosure.

Vague Triggers

Medium
Confidence
94% confidence
Finding
The skill description says it should be used when anyone mentions broad concepts like client projects, freelance work, invoices, proposals, deadlines, or follow-up. That creates a high chance of over-invocation during ordinary business conversation, causing the agent to activate persistence and CRM behavior when the user may only be discussing work generally. In this skill, over-triggering is more dangerous because the skill stores sensitive client and project data and is instructed to read and write persistent records automatically.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The skill persistently stores client names, contact details, communication notes, invoices, and project history in `client-data.json`, but it provides no user-facing warning, consent flow, retention guidance, or privacy notice. This is dangerous because users may unknowingly cause sensitive business and personal data to be retained across sessions, increasing the risk of unintended collection, surprise persistence, and exposure of confidential client information.

Static analysis

No suspicious patterns detected.