Skills/Glama/terminal-mcp

terminal-mcp@1.0.0

BLOCKED· install only

Publisher claims: "Enables executing shell commands and rendering their ANSI-colored output as styled PNG terminal screenshots with selectable themes, window chrome, watermarks, and timestamps. Useful for pentest reports, documentation, and professional terminal captures." Observed in sandbox: reads credential files, sends data to storage.googleapis.com.

Registry GlamaPublisher joasasantos · publishing for 11 daysInstalls 0Last detonated 11d ago

Coverage

Install scripts ran; no agent task scenario for this bundle.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What this means for the label: Blocked 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.

Revoked: guards refuse to launch this version

confirmed incident: read ~/.npmrc; contacted storage.googleapis.com (undeclared) Every machine running vet-skills guard stops starting it at the next launch; the state clears when the honeypot re-run or a reviewer clears it.

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the codeAlso nodesource.com, nodejs.org — not the publisher's domain; check what for before connecting.
What we saw when it ran
read ~/.npmrc · contacted storage.googleapis.com (undeclared)
What we could not test
use of the skill by an agent

Do not connect it. The honeypot or a critical finding blocked this version; the evidence is below.

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; install scripts ran; no agent task scenario for this bundle) on 2026-11-09 and scored it 30/100 (Blocked). Do not install it: the sandbox observed behaviour consistent with credential theft, exfiltration or persistence. Notable findings: Privileged sudo command; Privileged sudo command; Privileged sudo command. Summary: reads credential files, sends data to storage.googleapis.com.

Behavior trace

Honeypot run · 29 s · 2 scenarios
t+CategoryObserved action
13sfilesystemread ~/.npmrc
13sfilesystemread ~/.dpkg.cfg · ~/.npm/_logs · ~/.npm/_cacache/index-v5/e1/c1/b652b100dbb3a5a73667352080ee1a3571f2367294dfaedabb31c272d1c0 · ~/.npm/_cacache/index-v5/88/5d/25679281b30cf75a621bf8d7e1b724abec207e5af6227dfcf8f503319558 · ~/.npm/_cacache/index-v5/83/ee/cbc6649f11de3ace7a33d2b87588072d82973673c2fe9cd893d6f5522dca · ~/.npm/_cacache/index-v5/a3/a6/42066d98c9edb848e0640920496978d999c49eb48eb1bf9a3459169488a3 outside project
13sfilesystemwrote ~/.npm/_cacache/tmp/e2137e86 · ~/.npm/_cacache/tmp/f7d6e457 · ~/.npm/_cacache/tmp/7759fc5b · ~/.npm/_cacache/tmp/d6bd8487 · ~/.npm/_cacache/tmp/89abda50 · ~/.npm/_cacache/tmp/d583eb15
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://storage.googleapis.com:443 · not in the allow-list, refused
13snetworkCONNECT tcp://registry.npmjs.org:443
13snetworkCONNECT tcp://registry.npmjs.org:443
13sprocessexec /usr/bin/dirname
13sprocessexec /usr/bin/uname
13sprocessexec /usr/bin/sed
13sprocessexec /usr/bin/cut
13sprocessexec /usr/bin/dpkg
13sprocessexec /app/apps/web/node_modules/.bin/dpkg-query
13sprocessexec /root/.cache/node/corepack/v1/pnpm/10.28.0/dist/node-gyp-bin/dpkg-query
13sprocessexec /app/node_modules/.bin/dpkg-query
13sprocessexec /pnpm/dpkg-query
13sprocessexec /usr/local/sbin/dpkg-query
13sprocessexec /usr/local/bin/dpkg-query
13sprocessexec /usr/sbin/dpkg-query
13sprocessexec /usr/bin/dpkg-query
13sprocessexec /usr/bin/tail
13sprocessexec /usr/local/bin/npm
13sprocessexec /usr/local/bin/npx
13sprocessexec /tmp/ks-detonate-O4yE8b/setup/home/.npm/_npx/1d6e82a4126006c4/node_modules/.bin/tsc
13sprocessexited 1: (Use `node --trace-warnings ...` to show where the warning was created)
13sprocessscript backend runs setup only
13sprocessscript backend runs setup only
17sprocesssecond launch, clock +45 days, CI unset
29sfilesystemread ~/.npmrc
29sfilesystemread ~/.dpkg.cfg · ~/.npm/_logs · ~/.npm/_cacache/content-v2/sha512/a7/86/bd23a5fa9eee888681a606a01c6c9cb59a50b88f6eef10f657f45e0be3fbd94f72f2ab5564147c3f57f3d4701f41ba8f831b7887913d31dd0c9ae7ccdcde · ~/.npm/_cacache/content-v2/sha512/b5/5a/6c256ec376379c0221696c80757b7ab1210b04e8da0f739fde4ddadb6c80b88742d5b16867a1ade0fa6d87725048ba31f3b31678549540f8652e736fcb07 · ~/.npm/_cacache/content-v2/sha512/3b/f3/e07e7a53d712920de4184827d12391b2de13dff7598a543b982d41d924c883169b6f3f8d4c4a75a87e6f1d9c29b4db9e9935f64833b0d2cee48c0059e31c · ~/.npm/_cacache/content-v2/sha512/97/84/a9fc346c7a8afdc0be84bd5dbe4ee427eb774c90f8d9feca7d5e48214c46d5f4a94f4b5c54b19deeeff2103b8c31b5c141e1b82940f45c477402bdeccf71 outside project
29sfilesystemwrote ~/.npm/_cacache/index-v5/4a/17/b1eff28ef51b9d2d2ffa2c0f843021b3b14574502ac640bd97603ba7a60e · ~/.npm/_cacache/index-v5/04/5a/2b5d7a7c407d85d746baa0f5c9388a333e35a717a8a0a81943daa6cb1364 · ~/.npm/_cacache/index-v5/3b/23/a40ce913eeb42e9b680d585a876cd0deb84edca64589432795d76d515daa · ~/.npm/_cacache/tmp/b1615420 · ~/.npm/_cacache/index-v5/bb/47/13d204c6167b3bd8bfef533653b56005100b28d96dc7a016ab17fd6f0d73 · ~/.npm/_cacache/tmp/d1d160ed
29snetworkCONNECT tcp://registry.npmjs.org:443
29snetworkCONNECT tcp://registry.npmjs.org:443
29snetworkCONNECT tcp://registry.npmjs.org:443
29snetworkCONNECT tcp://storage.googleapis.com:443 · not in the allow-list, refused
29snetworkCONNECT tcp://storage.googleapis.com:443 · not in the allow-list, refused
29snetworkCONNECT tcp://registry.npmjs.org:443
29sprocessexec /usr/bin/dirname
29sprocessexec /usr/bin/uname
29sprocessexec /usr/bin/sed
29sprocessexec /usr/bin/cut
29sprocessexec /usr/bin/dpkg
29sprocessexec /app/apps/web/node_modules/.bin/dpkg-query
29sprocessexec /root/.cache/node/corepack/v1/pnpm/10.28.0/dist/node-gyp-bin/dpkg-query
29sprocessexec /app/node_modules/.bin/dpkg-query
29sprocessexec /pnpm/dpkg-query
29sprocessexec /usr/local/sbin/dpkg-query
29sprocessexec /usr/local/bin/dpkg-query
29sprocessexec /usr/sbin/dpkg-query
29sprocessexec /usr/bin/dpkg-query
29sprocessexec /usr/bin/tail
29sprocessexec /usr/local/bin/npm
29sprocessexec /usr/local/bin/npx
29sprocessexec /tmp/ks-detonate-O4yE8b/later/home/.npm/_npx/1d6e82a4126006c4/node_modules/.bin/tsc
29sprocessexited 1: (Use `node --trace-warnings ...` to show where the warning was created)

Static findings

HIGH
Privileged sudo commandsetup.sh:72 · Privileged sudo command — agent may execute with elevated privilegessudo pacman -S --noconfirm nss atk at-spi2-atk cups libdrm libxkbcommon \Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Privileged sudo commandsetup.sh:27 · Privileged sudo command — agent may execute with elevated privilegesecho " curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Privileged sudo commandsetup.sh:28 · Privileged sudo command — agent may execute with elevated privilegesecho " sudo apt-get install -y nodejs"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Privileged sudo commandsetup.sh:65 · Privileged sudo command — agent may execute with elevated privilegessudo dnf install -y \Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Privileged sudo commandsetup.sh:57 · Privileged sudo command — agent may execute with elevated privilegessudo apt-get install -y \Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
npx invocation of non-well-known packagesetup.sh:95 · npx invocation of non-well-known package — may execute untrusted codenpx tscFix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file pathssrc/index.ts:732 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files...env,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈37 tok
1 file · 8 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

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

What would make this Verified

50 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%

An override rule (credential_read_plus_egress) caps this verdict regardless of the score. The first item below has to go before anything else counts.

  1. Reads credential files≈ +27 on the totalThe sandbox saw reads under ~/.ssh, ~/.aws, ~/.npmrc, ~/.config or similar. Read only files inside the project, and only the ones the task needs.
  2. Contacts a host you did not declare≈ +23 on the totalList every host you talk to in SKILL.md frontmatter (`network: [api.example.com]`), or stop contacting the ones you cannot justify.
  3. Unclaimed publisher≈ +8 on the totalClaim joasasantos: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  4. Touches files outside the project≈ +7 on the totalKeep reads and writes inside the working directory, or declare the exact paths in `filesystem:` and explain why in the README.
  5. Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
  6. 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.
Publish a new version to Glama, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim joasasantosPropose a patch to the maintainer