Back to skill

Security audit

Usage Tracker

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward usage and cost tracker with disclosed local log storage, though users should be aware the logs persist on disk.

Install only if you are comfortable with usage metadata being saved locally. Review or delete usage-logs/api-cells.jsonl as needed, especially on shared machines or projects where model names, task types, or usage volumes are sensitive.

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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The skill explicitly states that usage logs are stored on disk in `usage-logs/api-cells.jsonl`, but it does not warn users that prompts, model identifiers, task types, and token metadata may be retained persistently. In a usage-tracking context, this can expose sensitive operational data or prompt contents if users assume the tool is ephemeral, especially on shared hosts or systems with weak file protections.

Static analysis

No suspicious patterns detected.