T02 · Agent Memory Poisoning
- Location
setup.md:60- Finding
Persistent Modification of Workspace Agent Routing
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill has a useful purpose, but it needs review because setup can persistently change agent routing and its commands run unpinned external CLIs.
Review this before installing. Decline or manually edit the AGENTS.md steering unless you explicitly want this skill loaded for future capability-related requests. Prefer pinned, reviewed versions of the clawhub and skills CLIs, inspect candidate skills before installation, and avoid sending sensitive task details as registry search queries.
setup.md:60Persistent Modification of Workspace Agent Routing
SKILL.md:149Execution of Unpinned Third-Party Packages Through npx
The setup promises that no data is written outside ~/skill-finder/, but later instructs modifying AGENTS.md outside that directory. This is dangerous because it misrepresents the skill's write scope and can lead users or higher-level agents to grant trust under false assumptions, enabling persistent behavioral changes beyond the declared boundary.
The document explicitly instructs adding routing lines to AGENTS.md, which exceeds the stated local-storage boundary and introduces persistence in a global agent-control file. Modifying routing/steering configuration can have long-lived effects on future agent behavior, potentially forcing this skill to load automatically and broadening its influence beyond the immediate task.
The top-level description says to use the skill whenever a user asks how to do something, improve a workflow, or install a capability. That scope is so broad it can trigger on ordinary requests and cause unnecessary search, external queries, or installation-oriented behavior in contexts where direct assistance would be safer and more appropriate.
The listed activation signals include generic phrases like 'How do I do X?' and 'Can you do this better?', which are common in routine conversations. Overbroad triggers can cause unintended invocation of a skill that sends queries off-machine and steers toward third-party code installation without sufficiently clear user intent.
The skill instructs use of npx clawhub without pinning a package version, which means execution depends on whatever version is currently resolved from the registry at runtime. That creates a supply-chain and reproducibility risk: a compromised, maliciously updated, or breaking new release could be fetched and executed implicitly.
The unpinned npx skills command executes whichever package version is resolved at runtime, exposing users to supply-chain tampering or unsafe upstream changes. Because this skill is specifically about discovery and installation, it normalizes repeated execution of remote CLI code, increasing exposure.
This line again directs use of unversioned npx clawhub, allowing silent drift to newly published code. Attackers who compromise the package or publish a harmful update could gain code execution when users follow the skill instructions.
This line again directs use of unversioned npx clawhub, allowing silent drift to newly published code. Attackers who compromise the package or publish a harmful update could gain code execution when users follow the skill instructions.
The search examples rely on unpinned npx clawhub, which still requires fetching/executing remote package code. Even though the operation is 'search', compromise of the CLI would affect the local machine before any skill recommendation is made.
The search examples rely on unpinned npx clawhub, which still requires fetching/executing remote package code. Even though the operation is 'search', compromise of the CLI would affect the local machine before any skill recommendation is made.
This line continues the pattern of unpinned runtime package execution via npx clawhub. Because the skill may be activated often, repeated use compounds the chance of pulling an unexpected or malicious release.
This line continues the pattern of unpinned runtime package execution via npx clawhub. Because the skill may be activated often, repeated use compounds the chance of pulling an unexpected or malicious release.
The install command uses unpinned npx clawhub, so two trust boundaries are crossed at once: first the CLI package itself, then the selected skill package. A compromise in the CLI distribution path could subvert even otherwise safe install decisions.
The install command uses unpinned npx clawhub, so two trust boundaries are crossed at once: first the CLI package itself, then the selected skill package. A compromise in the CLI distribution path could subvert even otherwise safe install decisions.
The command reference for npx clawhub search is unversioned, preserving the same supply-chain execution risk throughout the skill. Reference sections are especially important because users often copy-paste them directly.
npx clawhub inspect <slug> is also unpinned, so a user performing a supposedly safer inspection step still executes potentially unreviewed latest code. That weakens the skill's stated security posture around reviewing candidates before installation.
The install command again uses unpinned npx clawhub, which could allow malicious or unexpected behavior before or during installation. Since installation changes the environment, the consequence of a compromised CLI is more severe than a purely informational command.
Listing installed skills with unpinned npx clawhub list still carries runtime package execution risk from the registry. The operation being read-only in intent does not reduce the underlying trust issue of executing latest remote code.
The npx skills find reference is unversioned, creating the same supply-chain exposure as other npx uses. Because this ecosystem is described as broad and open, careful control of the CLI version is especially important.
npx skills add without a pinned CLI version can execute unreviewed latest CLI code while also installing third-party skill content. That creates layered supply-chain risk and undermines the otherwise cautious consent language in the document.
The unpinned npx skills list command still relies on runtime resolution of package code. Even non-install actions should not normalize executing an unspecified latest package in a security-sensitive workflow.
npx skills check is another unversioned remote CLI execution point. Security-checking commands are particularly sensitive because users may trust them more, but the tool performing the check is itself not pinned.
The update command references unpinned npx skills, which could pull different tool behavior over time and execute compromised code. Update workflows should be especially controlled, not left to latest-version resolution.
The example install string from skills find still shows unpinned npx skills add, encouraging users to copy-paste an unsafe invocation pattern. Example commands strongly influence actual operator behavior, so this is a practical rather than theoretical risk.
This line continues the copy-pasteable unpinned npx skills add pattern. In a skill whose purpose is to help install more code, unpinned bootstrap tooling materially increases attack surface.
No suspicious patterns detected.