T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:17- Finding
Auto-Approved Cloud Agent Commands Permit Unattended Local Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is for remote AI pair programming, but it gives cloud agents broad unattended control over local commands, files, installation steps, and possibly a real browser profile.
Install only if you intentionally want CellCog cloud agents to operate on your machine without per-command prompts. Use a disposable or tightly scoped project directory, avoid workspaces containing secrets, do not grant access to personal browser profiles or sensitive repositories, and prefer manually verifying any desktop installer, version, signature, and command before running it.
SKILL.md:17Auto-Approved Cloud Agent Commands Permit Unattended Local Execution
SKILL.md:94Server-Provided Installation Commands Can Introduce a Mutable Remote Payload
SKILL.md:27Third-Party Skill Dependencies Are Installed Without Immutable Version Pinning
The description advertises terminal access, file operations, and full development workflows as 'auto-approved for agents,' normalizing autonomous code execution on the user's machine without manual checkpoints. In the context of a skill that bridges cloud agents to a local desktop app, this creates a highly dangerous trust boundary where prompt mistakes, malicious tasks, or compromised upstream agents can directly alter the host system.
---
name: pair-programming-cellcog
description: "AI pair programming powered by CellCog Desktop. Code, debug, refactor, and build directly on the user's machine. Terminal access, file operations, full development workflows — auto-approved for agents."
author: CellCog
homepage: https://cellcog.ai
metadata:
The skill explicitly enables cloud agents to run commands, read files, and write code on the user's machine with auto-approval, but it does not present a prominent warning about the system and data impact of that autonomy. In this context, omission is dangerous because users or upstream agents may invoke the skill without understanding that local files and execution are being delegated to a remote service with broad machine access.
The file describes local machine data being explored and reasoned over by CellCog cloud agents, yet it lacks a direct warning that project contents, logs, configs, and other local data may be transmitted to or processed by a cloud service. That omission materially increases privacy and confidentiality risk, especially because the skill is marketed as fully autonomous and suitable for broad coding workflows.
This line states that all commands are auto-approved and fully autonomous with no manual approval needed, while the surrounding text grants command execution and file access on the user's machine. That combination substantially increases the blast radius of prompt injection, task misinterpretation, or remote service compromise, because destructive actions can occur immediately on the local host.
Co-work turns any machine into CellCog's workspace. CellCog Desktop acts as a bridge: CellCog's cloud agents coordinate with the desktop app to run commands, read files, and write code directly on the user's machine.
All commands are **auto-approved** for SDK/agent users — fully autonomous, no manual approval needed.
## Prerequisites
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
Although presented in a security section, 'Even with auto-approve' confirms that autonomous execution remains the operating mode and may create false confidence that listed protections are sufficient. The claimed blocked paths and redaction controls do not eliminate risks such as destructive edits, access to adjacent sensitive project data, abuse of available developer tooling, or indirect secret exposure through allowed directories.
## Security
Even with auto-approve, these protections are always active:
- **Blocked paths**: `~/.ssh`, `~/.aws`, credential files are inaccessible
- **Output redaction**: Sensitive data is automatically redacted from command output
- **Per-chat scoping**: Each chat session is scoped to its working directory
No suspicious patterns detected.