call-grokbot@0.1.1
VERIFIED· install onlyPublisher claims: "Enables Codex and Claude Code to send a self-contained task to an existing Grok Bot, read incremental replies, and interrupt the bot’s current turn while preserving its existing conversation, memory, and connected tools." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- 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: 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
CALL_GROKBOT_API_KEYCALL_GROKBOT_AUTH_MODECURSOR_API_KEYCURSOR_API_KEY_FILEConfiguration, not credentials: CALL_GROKBOT_AGENTS, CALL_GROKBOT_API_BASE_URL, CALL_GROKBOT_CURSOR_CLI, CALL_GROKBOT_DISABLED_TOOLS, CALL_GROKBOT_LIVE_AGENT, CALL_GROKBOT_STATE_DIR, CURSOR_SERVICE_ACCOUNT_KEY, NPM_CONFIG_CACHE, NPM_CONFIG_GLOBALCONFIG, NPM_CONFIG_USERCONFIG, XDG_STATE_HOME- Where it talks to
- no vendor host named in the codeAlso cursor.com, cursor.sh — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names cursor.com, cursor.sh as well as its own vendor. The guard injects CALL_GROKBOT_API_KEY, CALL_GROKBOT_AUTH_MODE, CURSOR_API_KEY, CURSOR_API_KEY_FILE only into requests to the host you bind (and its subdomains) and refuses the rest.
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 (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-11 and scored it 81/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 · 0 s · 1 scenarios · 0 deviationsStatic findings
const clean = { ...env };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env: { ...env, ...config.env },Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz login` and complete the official Cursor browser flow.Fix: Pin versions and sources; vendor anything fetched at install time.`npx --yes https://registry.npmjs.org/call-grokbot/-/call-grokbot-0.1.1.tgz login` in their terminal and complete the officialFix: Pin versions and sources; vendor anything fetched at install time.export const LOGIN_COMMAND = `npx --yes call-grokbot@${VERSION} login`;Fix: Pin versions and sources; vendor anything fetched at install time.'The contact state is unreadable or damaged. Restore state.json from a backup before sending another task; pending sends must not be silently forgotten.',Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.'https://user:[email protected]',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.import { chmod } from 'node:fs/promises';Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.Cost to the agent
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.