ClawHub
Back to skill

Security audit

Lensmor Event Fit Score

Security checks for vulnerabilities and agentic risk

Overview

This Markdown-only skill coherently uses a Lensmor API key to score trade-show fit and does not show hidden persistence, local data harvesting, or destructive behavior.

Install only if you intend to use Lensmor's external API for trade-show scoring. Treat LENSMOR_API_KEY as a secret, avoid pasting real tokens into shared prompts or screenshots, and be aware that event queries and Lensmor company-profile context may be used by the Lensmor service to compute scores.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • System Prompt LeakageDirect Leakage, Indirect Extraction, Tool-Based Exfiltration
  • 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
Findings (5)

Direct Prompt Extraction

High
Category
System Prompt Leakage
Confidence
85% confidence
Finding

Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.

Content

Scanner excerpt · SKILL.md (reported line 177)May include surrounding context.

md
| Score < 65 | Run `trade-show-finder` to identify better-fit alternatives |
| Multiple shows to compare | Score each via this skill, then rank by `score` field |

## Output Rules

1. All URLs formatted as `[text](url)` — never bare links
2. Never output the value of `LENSMOR_API_KEY`

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · README.md (reported line 46)May include surrounding context.

md
- Lensmor API key (`uak_your_api_key`) — contact [hello@lensmor.com](mailto:hello@lensmor.com) to purchase
- Base URL: `https://platform.lensmor.com`
- Full API docs: [https://api.lensmor.com/](https://api.lensmor.com/)

## Install

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill description contains very broad trigger phrases such as 'worth attending', 'should we exhibit', and multilingual equivalents that can match ordinary business conversation. Over-broad invocation is a real safety issue because it can cause the skill to activate in unintended contexts and initiate external API-driven behavior with potentially sensitive company context or paid resources.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · examples/hannover-messe-iot-vendor.md (reported line 10)May include surrounding context.

Step 1: Resolve Event ID

bash
curl -X GET "https://platform.lensmor.com/external/events/list?query=Hannover+Messe+2026" \
  -H "Authorization: Bearer uak_your_api_key"

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
84% confidence
Finding

This markdown file includes curl commands that require an API key in the Authorization header, but the surrounding instructions do not warn users that they are handling sensitive credentials or advise protecting them from shell history, screenshots, or sharing. Under the markdown-specific warning criterion, credential-related behavior should be disclosed when it may affect privacy or security.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.