T09 · Insecure Skill Coding Practices
- Location
SKILL.md:9- Finding
Plaintext Personal Employment and Compensation Information
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 9-16
Vulnerability Type: Plaintext sensitive data exposure
Risk Level: MediumEvidence
markdown Context for Tej's Senior PM role at Better Mortgage. ## Role - **Title:** Senior PM, Borrower Communications - **Focus:** Call routing, dialers, CRM systems, speed-to-lead optimization - **Team:** Leads a team focused on lead intake → loan officer connection - **Start Date:** December 2, 2024 - **Compensation:** $217K base + 15% bonus + 3,200 RSUs (4yr vest, quarterly, granted $10, current $29) - **First RSU vest:** March 2, 2025 (800/yr = 200/quarter)Technical Analysis
The reusable Skill stores personally attributable employment and financial information in plaintext. The exposed information includes the individual's employer context, role, start date, salary, bonus, equity allocation, grant valuation, current valuation, and vesting schedule.
Most declared Skill workflows—such as meeting preparation, project tracking, team coordination, and metrics analysis—do not require compensation or equity details. Loading this Skill therefore introduces sensitive information into the agent context beyond the principle of data minimization. The information could subsequently appear in model output, prompts sent to integrated services, execution logs, conversation archives, repository copies, or diagnostic traces.
This is a confidentiality weakness rather than a code-execution vulnerability. The audited project contains no scripts, dependencies, network retrieval logic, persistence mechanisms, or executable payloads.
Attack Path
- An attacker obtains read access to the Skill package, a repository copy, an agent transcript, or logs containing the loaded Skill context.
- Alternatively, an attacker with access to an agent session prompts the agent to summarize, repeat, or use the personal context loaded from the Skill.
- The attacker extr ...[truncated 986 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove salary, bonus, RSU valuation, vesting dates, and other financial details from
SKILL.md. - Replace personally identifying context with the minimum role-based information needed for the declared workflows, such as a generic job title and functional responsibilities.
- If sensitive employment data is genuinely required, retrieve it only when explicitly requested from an access-controlled source rather than embedding it in a reusable Skill.
- Require explicit user authorization before sensitive information is included in generated output or transmitted to an external integration.
- Restrict repository and Skill-package access using least-privilege controls, and review logs, backups, and prior repository history for copies of the exposed data.
- Add automated secret and sensitive-data scanning to the publication workflow, including checks for compensation, equity, personal dates, credentials, and other unnecessary personal information.
- Establish retention and redaction controls for prompts, transcripts, telemetry, and downstream tool output that may contain loaded Skill context.
- Remove salary, bonus, RSU valuation, vesting dates, and other financial details from
