Skills/Glama/carlos-flow

carlos-flow@2.5.9

CAUTION· not started

Publisher claims: "Enables a mechanical gating workflow for task intake, dispatch, independent review, verdict recording, auditing, and snapshot-based restoration through twelve stdio MCP tools." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher skyer-now · publishing for 7 daysInstalls 0Last detonated 7d ago
What would fix thisWatchDispute verdict

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

Code inventory arrives with this version's next honeypot run.
It will ask for
unknown until the next run
Where it talks to
unknown until the next run
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try carlos-flow` runs it now and prints the full answer.

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-07 and scored it 78/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 60 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
60sprocessdependency install exceeded 60s
60sprocessexec /usr/bin/date
60sprocessexec /usr/bin/timeout
60sclaimedno tools/list reply (exit 0)
60sprocessscript backend runs setup only
60sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathssrc/protocol.js:39 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files".env", ".env.local", ".env.development", ".env.production", ".env.test",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/card.js:7 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files'.env', '.env.local', '.env.development', '.env.production', '.env.test',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathspackage.json:64 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files".env.example",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/mutation-check.mjs:179 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv: { ...process.env, ...env },Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
References a credential file in the home directoryscripts/release.mjs:19 · References a credential file in the home directory// 2. npm 凭据：~/.npmrc 或项目 .npmrc.local 含有效 _authTokenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03
MEDIUM
Process kill commandtest/concurrency-e2e.mjs:43 · Process kill command — agent can terminate processes// 必须**每次运行唯一**：若复用固定路径，上一次运行残留的 server 进程（kill 不干净）Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

Cost to the agent

Instructions loaded
≈40 tok
1 file · 42 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim skyer-now: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  3. References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  4. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  5. Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
Publish a new version to Glama, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim skyer-nowPropose a patch to the maintainer