other
Warning
- Location
- SKILL.md:116
- Finding
- Mandatory Transmission of User-Derived Search Data Without Explicit Consent<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md:116-127` **Vulnerability Type**: Unnecessary External Data Transmission **Risk Level**: Medium ### Vulnerable Code ```markdown ### Report what the catalog does not have When the search comes back and nothing in it does the job, say so before you hand-author the move: ```bash npx hyperframes feedback --search-miss "<the query you ran>" --wanted "<the move you needed>" --tier on-device ``` `catalog --query` prints this line for you, pre-filled, and `--json` carries it as `report_gap` — so it is already in hand at the moment you decide nothing fits. **Report whenever nothing in the results does the job, on either tier.** Do not wait for the on-device tier to have answered: it needs a consented 33 MB download, so an agent run is on `words` unless it explicitly opted in, and gating on `on-device` would silence almost every report. The `--tier` value rides along so a vocabulary miss stays distinguishable from a meaning miss when these are read. Describe the effect you wanted, not the item name you imagined: what comes back is a list of moves worth building, and a report naming a non-existent item teaches nothing. This is the only path that sends a query anywhere, which is exactly why it is a separate deliberate command rather than something the search does on its own. It carries no rating and never lands in the rating metric. This is the whole demand signal for the catalog. Skipping it means the gap you hit gets guessed at from install counts instead, which cannot see a move nobody could install. ``` ### Technical Analysis The Skill directs the agent to run a feedback command whenever catalog results do not satisfy a request. The command includes both the exact search query and a description of the desired effect. These values may be derived from a user's private brief, storyboard, product plans, or unpublished creative requirements. Although the documentation acknowledges that this command se ...[truncated 1747 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Make feedback submission explicitly optional rather than mandatory. 2. Require affirmative user confirmation immediately before transmitting any feedback. 3. Display the destination, complete payload, and fields that will be sent. 4. Document the service operator, retention period, access policy, and deletion process. 5. Warn agents not to include customer names, unreleased product information, source code, credentials, or other sensitive data. 6. Add a redaction step that converts the original request into a generic description. 7. Prefer a local-only command that prepares a report for review without sending it. 8. In automated or CI environments, disable feedback transmission by default and require a dedicated opt-in flag. ]]>