Versioned security assessment

Report ID: SA-B8C1BCE2

7/7/2026, 11:42:37 PM

happyhorse-1-0 security assessment v5

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
happyhorse-1-0
Version
v5
Maintainer
agentspace-so
Source
github.com/agentspace-so/runcomfy-agent-skills/tree/main/happyhorse-1-0/
Coverage
1 Files scanned · 196 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

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.

The real risks are the intended RunComfy CLI executions, global setup commands, and the disclosed POST to the RunComfy Model API. Most other static findings are Markdown backtick, REST ellipsis, documentation link, or standard credential-store false positives.

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

9 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
SKILL.md:10
Ruby/shell backtick execution
Calls `runcomfy run happyhorse/happyhorse-1-0/text-to-video` through
The front matter states the skill calls the local RunComfy CLI. That is an intended external command execution path, even though the command target is specific.
Medium
SKILL.md:24-26
Ruby/shell backtick execution
```bash
The fenced block contains an npx command that installs the skill globally. Running package-manager installation commands is a real supply-chain and system-modification risk.
Medium
SKILL.md:44-45
Ruby/shell backtick execution
1. **RunComfy CLI** — `npm i -g @runcomfy/cli`
The prerequisite tells users to run a global npm install for the RunComfy CLI. This is legitimate setup guidance but still executes external package-manager code.
Medium
SKILL.md:45-46
Ruby/shell backtick execution
2. **RunComfy account** — `runcomfy login` opens a browser device-code flow.
The prerequisite tells users to run runcomfy login, which invokes a local CLI authentication flow. This is expected behavior but involves local command execution and credential handling.
Medium
SKILL.md:65-69
Ruby/shell backtick execution
```bash
The example invokes runcomfy run with user-supplied prompt data and an output directory. The command is hardcoded, but it still executes a local CLI process.
Medium
SKILL.md:73-82
Ruby/shell backtick execution
```bash
The vertical short example invokes runcomfy run with generation settings and user prompt data. This is intended external command execution through the local CLI.
Medium
SKILL.md:86-90
Ruby/shell backtick execution
```bash
The cheaper test-pass example invokes runcomfy run with user prompt data. The command target is fixed, but it remains a real external command surface.
Medium
SKILL.md:178-179
Ruby/shell backtick execution
1. The skill invokes `runcomfy run happyhorse/happyhorse-1-0/text-to-video` with a JSON body matchin
The how-it-works section explicitly says the skill invokes runcomfy run with a JSON body. That confirms the intended local CLI execution behavior.
Medium
SKILL.md:179
Hardcoded URL
2. The CLI POSTs to `https://model-api.runcomfy.net/v1/models/happyhorse/happyhorse-1-0/text-to-vide
The documented CLI POST sends the user bearer token and prompt data to the RunComfy Model API. This is disclosed and expected, but it is a real outbound data flow.

Risk findings

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

No confirmed security findings were recorded for this completed audit.

Remediation

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

  1. FIX-001
    Medium
    Local CLI and package-manager commands are part of normal use.
    Require clear user confirmation before install, login, or generation commands, and document how to verify the RunComfy CLI package.
  2. FIX-002
    Medium
    Prompts and bearer-token authenticated requests are sent to RunComfy.
    Keep the outbound endpoint disclosure prominent and remind users not to submit sensitive prompt data unless approved.
  3. FIX-003
    Low
    Generated files are downloaded into a user-selected output directory.
    Recommend a dedicated output directory and preserve the documented host whitelist and file-size cap.

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

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

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

Audit attestation: not_attestable