Skills/Glama/inbound-guard

inbound-guard@0.1.0

VERIFIED· startup only

Publisher claims: "Enables an agent that reads a person's inbox to check a raw or .eml message and receive a 0-100 cold-outreach score with the reasons behind it. The agent can then avoid replying on the person's behalf to a cold message, or surface a likely cold one with its signals for the person to judge." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher analyzemail · publishing for 0 daysInstalls 0Last detonated 6 h ago
$npx skills add inbound-guard
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

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

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the codeAlso rdap.org — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- <the server's command>

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; startup only; authenticated tool behavior not tested) on 2026-11-19 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 20 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
20sclaimedstartup only: exited (0) before answering · --fail-on <level> Exit 1 at this verdict or worse: cold (default) or likely. --json Machine-readable output. --no-colour Plain text. Exit code 0: not cold. 1: cold (or likely, with --fail-on likely). 2: could not run.
20sprocessscript backend runs setup only
20sprocessno install scripts to re-run

Static findings

No findings across 1,268 lines in 14 files.

Cost to the agent

Instructions loaded
≈38 tok
1 file · 14 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.