Versioned security assessment

Report ID: SA-62E2A730

7/5/2026, 8:01:36 PM

happyhorse-1-0 security assessment v3

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
happyhorse-1-0
Version
v3
Maintainer
runcomfy-com
Coverage
1 Files scanned · 196 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

High

1 confirmed security finding requires attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Most static findings are false positives from Markdown backticks, fenced examples, and abbreviated HTTP paths. Confirmed residual risk is limited to intended RunComfy CLI execution and network submission of prompts and bearer-token-authenticated requests. A high-confidence semantic supply-chain issue remains because install instructions reference a different GitHub repository than the reviewed source metadata.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

1 Files scanned · 196 Lines analyzed

10 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 4 evidence locations

Filesystem access

May read or write local files.

Observed in 4 evidence locations

Env variables

May read values from the process environment.

Not recorded by this audit

External commands

May invoke commands or programs outside the Skill.

Observed in 40 evidence locations

Capability review items (9)
Medium
Ruby/shell backtick execution
Calls `runcomfy run happyhorse/happyhorse-1-0/text-to-video` through
The skill states that it calls the local RunComfy CLI to launch a hosted text-to-video job. The command is fixed and legitimate, but it is still an external process that sends user content outside the local environment.
Medium
Ruby/shell backtick execution
```bash
The fenced block contains an npx/global skill installation command. This appears legitimate, but running it executes external tooling and should require explicit user confirmation.
Medium
Ruby/shell backtick execution
1. **RunComfy CLI** — `npm i -g @runcomfy/cli`
Line 44 instructs users to install the RunComfy CLI globally through npm. This is a normal prerequisite, but it executes package manager code outside the skill itself.
Medium
Ruby/shell backtick execution
2. **RunComfy account** — `runcomfy login` opens a browser device-code flow.
Line 45 instructs users to run runcomfy login, which starts an authentication flow for account access. The action is expected, but it handles credentials and should be user-approved.
Medium
Ruby/shell backtick execution
```bash
The command example invokes runcomfy with user-supplied prompt data and an output directory. The CLI target is fixed, but this is real external command execution.
Medium
Ruby/shell backtick execution
```bash
The vertical-video example invokes runcomfy with prompt data and generation settings. It is legitimate product behavior, but it still launches a local external command.
Medium
Ruby/shell backtick execution
```bash
The cheaper test-pass example invokes runcomfy with prompt data and generation settings. The command is fixed, but an agent could execute it locally if authorized.
Medium
Ruby/shell backtick execution
1. The skill invokes `runcomfy run happyhorse/happyhorse-1-0/text-to-video` with a JSON body matchin
The skill explicitly says it invokes runcomfy run with a JSON body. This is intended external CLI behavior rather than arbitrary execution, so the risk is limited but real.
Low
Hardcoded URL
2. The CLI POSTs to `https://model-api.runcomfy.net/v1/models/happyhorse/happyhorse-1-0/text-to-vide
Line 179 identifies a POST to the RunComfy model API using the user bearer token. This is intended service use, but it is real network egress of prompt data and credentials.

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (1)

RISK-001 High
Repository Mismatch in Installation Instructions
The skill links to and installs from agentspace-so/runcomfy-skills while the reviewed source metadata points to runcomfy-com/skills. This can route users to code that differs from the reviewed source.
The GitHub link and npx install command name agentspace-so/runcomfy-skills, while the report metadata identifies runcomfy-com/skills as the reviewed source. This is a clear supply-chain consistency issue, although ownership relationship is not proven from the file alone.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    High
    Repository mismatch in public links and install command.
    Update the GitHub link and npx install command to the reviewed repository, or document a verified ownership relationship between both repositories.
  2. FIX-002
    Medium
    External RunComfy CLI execution is part of normal use.
    Require explicit user approval before running npx, npm, runcomfy login, or runcomfy run commands from this skill.
  3. FIX-003
    Low
    Prompts and bearer-token-authenticated requests are sent to RunComfy.
    Disclose the external API submission clearly and avoid sending confidential prompts unless the user accepts that transfer.
  4. FIX-004
    Low
    RunComfy token storage is security-sensitive.
    Keep token files owner-only, prefer environment-scoped tokens in CI, and never print token file contents in generated instructions.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Verify and export

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable